I have a complex SetupBuilder install that I want to trick up a bit.
Here's the situation:
From one SB build the potential customer can install the program but cannot
enter more than 30 names into the database until they contact me and I give
them their Registration Number (See Attachment).
This works well except that after a year I want to prevent them downloading
the Free Trial and updating their program without signing up for year
maintenance subscription.
Embedding a date in the security file doesn't really help because one
customer may have many dates (one for each program he installs). But has
only one renewal date no matter the number of installs.
One approach I considered was to have the Security file deleted each time a
new version is installed requiring re-registration. This would be a PITA
for me and the customer but would work.
So I was hoping to have one SB script that would delete or not delete the
security file depending where they downloaded from (my demo page or a
password restricted Customers Only page).
Anyway I hope maybe some SB magic could be applied. ;-)
Any ideas ?
--
Lynn Howard
Linked Software
www.linkedsoftware.com