Server scheduled scripts have a number of limitations that can make using them a challenge. One of them is that only relative path references to external data source references will work. If your FileMaker files are not all in the same folder, the references don't work. Also, you can not use Import records to move data from one file to another directly in a server scheduled script. If you pick your file locations carefully, it's possible to do it, but you have to export the data to a text file then import it from the text file into the destination file.
See this knowledgebase article: http://help.filemaker.com/app/answers/detail/a_id/7035/kw/server%20import%20records
The alternative to a server scheduled script is to set up a FileMaker Pro "robot file" that connects as a client to the hosted files and performs the needed script. Since this runs from a client session instead of on the server side, it does not have these limitations. You can use Windows Task Manager to schedule when such a robot file opens and runs on windows systems. There's also a Mac equivalent you can use for the same purpose.
Thanks for the reply! All makes sense. The files are not in the same folder which makes me regret not doing that in the first place!
All of my databases run on the same physical hardware --- they are in their own folders.
What is the easiest method for me to MOVE the SLAVE database into the same folder as MASTER? I am not using the import records feature but I would like the scripts to work within the limitations you have outlined --- and there is nothing to stop me putting these databases into the same physical folder.
SO --- that being the case, on the server, what is the easiest way to move the file? Remove from database and reupload? Or is there a much easier trick?
You can use the admin console to close the files. Then just use your OS inteface to open the folder where they are located and move the files into a common folder. Then use the console to re-open them.