More details please.
I have a batch file that opens an opener file, which opens a remote Database and runs an export script to drop a file on my local machine.
I tried to create a system-level script schedule in Filemaker Server 9 Adv that runs the batch file.
When I test it out by using "run a the schedule now", the batch file does not run and nothing happens.
However, when I double-click on the batch file, it works just fine.... what gives?
Thanks, appreciate it Phil,
Just guessing here, but some system scripts have to be run from the windows operating system Task Manager instead of the server. That's what I encountered when I set up a VB Script to copy the most recent set of backup files across the network to another computer's hard drive.
TSGal or someone will tell us if I'm wrong.
Yeah, that's strange.
It says in the knowledge base that the FileMaker Server 9 scheduler should be able to run batch files. I was thinking of using the windows task scheduler if this didn't work but I like the email notification from FileMaker server scheduler.
It will run batch files, just like it will run VB Script files. However, if your script needs to access a location other than the local hard drive, you may have to use the Task Manager.
That's the thing Phil,
My batch script only needs to open a file (the opener file) that is located in the same local folder. Meaning both the batch file and the opener file are located in "C:\program files\filemaker\filemaker server\data\scripts".
That sounds like the "robot" file we discussed in another thread. I set up my robot with Window's "Scheduled Task" widget. I found I could install FMP 10 on the server and set up the "Scheduled Task" to open the file during the evening hours when the system is idle to kick off my client side script that can't run as a server side script. That seemed simpler than trying to write a system script to open the file and controlling it with Filemaker Server's scheduler.
That's just my preference, don't know why it doesn't work for you, though maybe some else can explain.
Yes Phil, this is the "robot" file discussed in our previous thread.
Looks like I'll just have to go with the windows scheduled task. Thanks again!