As you've discovered, you can't set a Schedule in server admin to run a script every other week. You could set the schedule to run the script every week and your script could check the date and exit without doing anything every other week. Is this what you had in mind?
Globals modified by server scheduled scripts are "host" modifications of the field, so changes to them will persist--unlike from a client run script.
Define a global date field, gNextFortNight and assign it the date of the first time the script will run.
In your script:
If [YourTable::gNextFortNight < get(currentdate ) ]
Set Field [YourTable::gNextFortNight ; YourTable::gNextFortNight + 14]
#do the rest of your script here
Thanks Phil, that sounds workable, will give it a go.
Actually, I like Mr Vodka's suggestion better. Unfortunately, you can't specify an "every n days" interval greater than 7. Ran into that when I wanted to run an extra back up once a month for long term archival purposes. :smileymad:
If I could have chosen 14 days, I wouldn't be asking this question :)
Apologies. At the time that you posted this thread I could not comment on FMS11. FMS11 allows for the user to set a custom number of days.
Another problem with running a script:
If you want to backup more than the max schedule interval can you do this from within a script?
My undertsanding is that databases hosted on Server or Server Advanced can't run the script step 'save a copy as' so you can't backup from within a script.
Is there another solution?
Since you can schedule a backup, why would you want to use "save a copy as"?