Quote:How about a program or method that I can employ to stop sesame from running after x amount of uses or time. I have had employees in the past take my program and use it to start a business like mine using my own program. I would like to protect against this in the future.
If you are going to use a converted bat to com file (bat2exe.com) like Bob suggested you could put a generic non descript file like sysk.bat or anything.txt and have the bat file check for its existence before it starts your Sesame application. It would look something like this
if exist c:\sysk.bat C:\Sesame\sesame.exe -splash c:\sesame\pics\yourfile.jpg c:\sesame\data\your.db
This will look in the c: directory for a file named sysk.bat if it finds it, it will run Sesame with your splash image and your database. It is not the cleanest method but it would work because the chances of someone knowing to put the fake file on their machine is very slim. Just a thought.
You could probably use a similar method using the Sbasic command FileExists() to trip up some major sub routine that would cripple your app if someone was to get your application as long as they can not access your program layout.
Quote:Finally does anyone know if there will be developer versions of sesame that will allow a more developer specific branding like our product name in the upper corner of the blue bar not sesame and then our program name or the ability to deactivate the help menu and only have the user use custom help.
This is a question only the Lanticans themselves could answer, however I would guess there are many, many, many tasks on their list before those.
But I do like some of the options you suggested. There is a method on the support page for submitting suggestions.