Scheduled Scripts

[JerrySalem]

Is it possible to use FM Server to schedule scripts to be run, INDEPENDANT of any users being on the system?

I would like my system to perfom some housekeeping functions, and send some automatic emails at night.

Presently, I have the last person out the door at night engage a script. But they often forget to do this.

I know about the plug ins, but I don't want to be dependant on a user to leave the solution open, or clicking buttons etc. What is the best way to implement this?

TIA

Jerry

[DykstrL]

Here's a way that might work for your situation:

I'm currently developing a server application that will send email based on the status of new or changed records in the files. I set up a dedicated workstation with regular FileMaker and a special email address that makes it look like it is coming from the server. I created a series of FMP files on the workstation controlled by a main file that basically has a script that runs constantly with some pauses set to certain times. At certain points in the script, it opens the other files that open the server files, runs some scripted finds for the targeted records and then creates and sends out email messages to users who need to take some action on those records. The main script then re-calls itself and starts all over.

I haven't used this in productions yet, but the testing we did shows that the concept works. The scheduled backups on the server don't seem to affect this permanently connected 'guest' - I just make sure the scripts aren't activated during the backup processes. I guess you could consider this workstation as an extension of the server.

I got this idea from a part of my backup routine that closes 2 product list files on the server, opens them in FMP via a separate file that exports, sorts, then re-imports the records. This helps to reduce opening times of the files for users with an initial sort of the records - It has worked like a dream for 3 years.

Both the server and workstation are NT4. The email workstation is set so a reboot automatically starts the main script file and it all runs unattended while the workstation is 'locked'.