[AccessD] Demo To Run for 30 Days

I store the state each time they start the system.  If the system date is 
ever earlier than the last time they started it (indicating that they moved 
the system date back to try to get a few more days' use) I give them a 
message that says they need to adjust the clock in the computer and quit the 
app.

Rocky

----- Original Message ----- 
From: "Josh McFarlane" <darsant at gmail.com>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Tuesday, July 26, 2005 8:12 AM
Subject: Re: [AccessD] Demo To Run for 30 Days


> 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
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>