OK I am 98% closest to the greatest evaluation DLL i've ever written, almost foolproof...
However, I put the date in the secret file, the date the program was last run, and if today's date doesn't match I increment "days", an integer value.
This is good, but lets say the program is installed and 45 days later they use it again, it should already be timed out, instead it will say it's on day 2.
So my idea is this:
Insert the install date in this file.
Each time the program is run, check the date and check todays date, do the math and figure out hwo many days have elapsed.
I know someone out there is a whiz at this stuff, and there has GOT to be an easier way than the way I'm conconcting...
Basically here's my one issue:
If the program is installed on June 18th for example and times out in 15 days I need ot do the math to figure this out say on July 4th.
Preciate any input
Scott
-------------
Scott
mailto:[email protected][email protected]</A>
MCSE, MCP+Internet
However, I put the date in the secret file, the date the program was last run, and if today's date doesn't match I increment "days", an integer value.
This is good, but lets say the program is installed and 45 days later they use it again, it should already be timed out, instead it will say it's on day 2.
So my idea is this:
Insert the install date in this file.
Each time the program is run, check the date and check todays date, do the math and figure out hwo many days have elapsed.
I know someone out there is a whiz at this stuff, and there has GOT to be an easier way than the way I'm conconcting...
Basically here's my one issue:
If the program is installed on June 18th for example and times out in 15 days I need ot do the math to figure this out say on July 4th.
Preciate any input

Scott
-------------
Scott
mailto:[email protected][email protected]</A>
MCSE, MCP+Internet
Comment