doing trial periods

[Monte Goulding]

>> example for binary read:
>> You have a stack which contains your expiration date
>> variable. lets say
>> its stored in a custom property. Now you put some date into it, lets
>> say "13.08.2004" (using German notation here). Then you can do this:
>>
>> on mouseUp
>>    put offset("13.08.2004", URL "binfile:/path/to/stack.rev") into
>> theFirstChar
>>    put "14.08.2004" into char theFirstChar to (theFirstChar + 9) \
>>    in URL "binfile:/path/to/stack.rev"
>> end mouseUp
>
>Does this work in an encrypted (password-protected) standalone?

If it's password protected then the file contents are encrypted so you
wouldn't find that string. Further, what's the advantage of this method over
setting an custom property and saving? There are more issues with this
method:
 - if you were changing the standalone then you would need to have a second
standalone to do it
 - any hacker worth his salt would notice the change in the modification
date of the standalone and find the string and change it to 2020
 - for this to work the file needs to be unpassword protected so anyone with
rev can break it in about 2 mins

I must say if it's possible to use crippleware in your app then that's the
safest way to go. Other than crippleware it's either impossible or
infeasable to have a safe demo model without requiring an internet
connection. Every other model requres saving the data somewhere which
ofcourse opens a gaping hole.

Cheers

Monte