Hmm, I didnt think I had to do that - once the date is reached the
counter is set to '2' which prevents the file from opening again.

I've had a play around with the script and can't seem to find a way to
bypass it - if i set the mac's clock forward and open it, it inserts the
future date in date started. When you reset the clock and open it, the
script compares the current date to the start date - if it see's the
current date is lower than the start date it will timout, return a
counter value of '2' and prevent further opening of the file.

If I set the mac clock into the past and do the same, it will obviously
see the date is well past the 30 days 'End Date' and timeout - again
returning '2' value in the counter and preventing further use of the
file.

Either way, unless you constantly change the clock back to the start
date every time you open it, there appears no way to get around it! :)

I did find one thing though - it is an idea to build in a fail-safe
should you lock yourself out of the file while testing it (I did just
that!).

Create a global text field called 'username' or whatever you want to
call it. Enter an obscure phrase or memorable numbers etc. Then delete
the field from the layout (but the contents remain, unviewable).

For this example we fill the field 'username' with 'bert'...

Allow User Abort [Off]
Set Error Capture [on]
If ["Status(CurrentUser)"="username"]
Exit Script
***rest of script continues here***

So when you run the script, if you lock (or time) yourself out, go to
Application Prefs in Filemaker and type in your secret username in the
'Custom' field.

Now when you re-open the file, it will see that your current username
matches the 'username' field and exit the script - leaving you free to
access the file!

Seems to work for me, just need to make sure nobody finds out the secret
username!

Numb