NewsArchive
05-11-2007, 01:53 AM
For some time I have provided free upgrades to my clients but am now
changing all that and providing 12 months upgrades free then charging after
12 months.
I currently use an installer and update product to collect upgrades from my
server based on a registry value on my users machine. Clearly that needs to
be controlled by date now. Incidentally I am seriously considering
purchasing Setup Builder now and have posed this to Friedrich to see if SUB
can help in any way. I know SUB can provide updates (I think) but based on
date of install?
Anyway at the moment I can only think of 2 ways to control the installation
date and that is by writing the value to a tps file (encrypted) or using a
registry entry hidden somewhere. Both are not safe because if the registry
is trashed or the application reinstalled (yes a client has deleted a live
copy before) then the date would be reset.
Handling individual client control manually is not an option because of the
numbers and having something on a server to check a database again is not
really an option at this time.
Does anyone have any ideas how to provide the safest check on whether
updates are to be allowed based on time after initial install? The ONLY
absolute check I do have is in my own administration database where I hold
the version and date of purchase.
Oh another thing that springs to mind that i did try but failed is that
someone may buy and we release a major version within the 12 months of
purchase that they would be entitled to. I release a major version on Jan1st
every year so someone who buys in September would be entitled to that free
so cannot use the version number to control things.
BTW I provide bugfixes free for life so I could have 2 installs (1 for
bugfixes the other for new features)
TIA
John Fligg
changing all that and providing 12 months upgrades free then charging after
12 months.
I currently use an installer and update product to collect upgrades from my
server based on a registry value on my users machine. Clearly that needs to
be controlled by date now. Incidentally I am seriously considering
purchasing Setup Builder now and have posed this to Friedrich to see if SUB
can help in any way. I know SUB can provide updates (I think) but based on
date of install?
Anyway at the moment I can only think of 2 ways to control the installation
date and that is by writing the value to a tps file (encrypted) or using a
registry entry hidden somewhere. Both are not safe because if the registry
is trashed or the application reinstalled (yes a client has deleted a live
copy before) then the date would be reset.
Handling individual client control manually is not an option because of the
numbers and having something on a server to check a database again is not
really an option at this time.
Does anyone have any ideas how to provide the safest check on whether
updates are to be allowed based on time after initial install? The ONLY
absolute check I do have is in my own administration database where I hold
the version and date of purchase.
Oh another thing that springs to mind that i did try but failed is that
someone may buy and we release a major version within the 12 months of
purchase that they would be entitled to. I release a major version on Jan1st
every year so someone who buys in September would be entitled to that free
so cannot use the version number to control things.
BTW I provide bugfixes free for life so I could have 2 installs (1 for
bugfixes the other for new features)
TIA
John Fligg