Richmond,

I don't know what your program does but if it allows the user to store data you 
could embed the timestamp in the data.

This is what I do with InfoWallet. The program InfoWallet itself isn't really 
timestamped but data files it creates are. When the datafile is created it gets 
a date stamp and that stamp is compared to the current date each time the file 
is opened. I give the users 50 days instead of 30 and if the 50 days are passed 
then the data file is simply not opened but the data itself is intact. Once the 
user purchases a license key the program no longer pays any attention to the 
date the file was created and they get access to all their entered data and can 
use it forever.

If the user passes the 50 days and still wants to experiment with the software 
then can simply create another data file but they would be starting the data 
from scratch. Because of this, the only functional limitation of the trial 
version is the inability to export the data back out. If I allowed that, the 
user could simply keep exporting and then importing into a new data file.

Bill Vlahos
_________________
InfoWallet (http://www.infowallet.com) is about keeping your important life 
information with you, accessible, and secure.

On Apr 23, 2012, at 1:32 AM, Richmond wrote:

> Um:
> 
> --30 Day code--
> 
> if the fld "STAMP" of stack "STAMP" is empty then
>  set the lockScreen to true
>    put the seconds into into fld "STAMP" of stack "STAMP"
>    save stack "STAMP"
>  set the lockScreen to false
> end if
> 
> put the seconds into DAZE30
> put fld "STAMP" of stack "STAMP" into TSTAMP
> if DAZE30 > (TSTAMP + 2592000) then
>  set the vis of img "TIME IS UP CHUM" to true
> end if
> 
> --End 30 Day code--
> 
> This works very well in a stack (where stack "STAMP" is a substack of my 
> mainstack),
> 
> will it work in a standalone?
> 
> [NOT unless I remove that double 'into' . . .  :) ]
> 
> or, put another way,
> 
> will the standalone save the time-stamp data in the substack?
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to