[AccessD] Demo To Run for 30 Days

Josh McFarlane darsant at gmail.com
Tue Jul 26 10:12:36 CDT 2005


On 7/26/05, paul.hartland at fsmail.net <paul.hartland at fsmail.net> wrote:
> What I tend to do is when they first open the application, store the system date and calculate 30 days in advance and also store this, then you just check the stored date which is 30 days in advance each time they open the app, if you check a stored date against system date, they can always keep changing the date on their machine can't they ?
> 
> Paul Hartland

The optimum solution I can think of is to have the two fields you
mentioned, and use them as sort of a between statement in which it can
run. First time the program opens, it sets both dates.

Next time the user opens the application, first it checks to make sure
the current date is between those dates, and if it is, it updates the
current system date with the new value. This way, the date window that
the program can be opened in slowly expires as time progresses.

If the user sets their computer to day X  time Y after they got the
App but before their last use time,  the start time is already after
the current time, and the program cannot open.

-- 
Josh McFarlane
"Peace cannot be kept by force. It can only be achieved by understanding."
-Albert Einstein



More information about the AccessD mailing list