Does anyone have any sample code that does software expiration in a way
that's a bit more sophisticated than moving ahead a clock?
*** Sent via Developersdex http://www.developersdex.com ***
Does anyone have any sample code that does software expiration in a way
that's a bit more sophisticated than moving ahead a clock?
*** Sent via Developersdex http://www.developersdex.com ***
You could use GetSetting and SaveSetting to write a time based figure to the
registry - but this would still be based on the users system time. Give an
example of what you would consider more sophisticated.
--
Regards,
Tom Ogilvy
"Larry" <[email protected]> wrote in message
news:%[email protected]...
> Does anyone have any sample code that does software expiration in a way
> that's a bit more sophisticated than moving ahead a clock?
>
> *** Sent via Developersdex http://www.developersdex.com ***
Something that's a bit more sophisticated is something that will look at
things a bit gradually. For instance, If i set the system clock
forward, run the application, and then move it back.
Under most scenarios, then things will not work any longer. What if
someone sets their system clock forward by mistake (like wrong year 2006
instead of 2005), only to move it back. It could be an error.
Make sense.
Have any creative ideas on how to work around this?
*** Sent via Developersdex http://www.developersdex.com ***
Not on a standalone machine (unless you want to limit the number of times
the file can be opened). On a Internect Connected machine, I suppose you
could query an external clock such as the Atomic clock.
--
Regards,
Tom Ogilvy
"Larry" <[email protected]> wrote in message
news:[email protected]...
> Something that's a bit more sophisticated is something that will look at
> things a bit gradually. For instance, If i set the system clock
> forward, run the application, and then move it back.
>
> Under most scenarios, then things will not work any longer. What if
> someone sets their system clock forward by mistake (like wrong year 2006
> instead of 2005), only to move it back. It could be an error.
>
> Make sense.
>
> Have any creative ideas on how to work around this?
>
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
Why not use Kernel32:GetTickCount function to accumulate no. of
milliseconds the program is running.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks