You will have to use a client to act as your robot machine to perform the script. With FM10, you may be able to use a Install On Timer step but if you need to run a script lets say at 10PM every day, you can just use a local opener file that calls the script in your remote file. The local opener file could be called using a event scheduler such as Windows scheduler or iCal.
Thanks for the idea... the problem I'm currently having is that the script I'm attempting to automate belongs to a remote database that is password protected. On my client/robot machine, I'm attempting to run the remote script locally, but every time I try to I'm prompted for my credentials in order to open the remote database.
Is there any way that I can store my Account Name and Password when setting up the remote data source so that I'm not prompted to log in each time? Obviously, if I'm setting up a process to execute a script automatically, I don't want the process to halt because it's waiting for me to type in a password every day.
If the same account you use to log into your remote file exists in your local file and your local file opens with that account ( set under File options), then it should pass it along.
Thanks, but this doesn't seem to be working. The only username and password I can use to open the local database file is "Admin" with a blank password.
You must create a user name in the local file that is the same user name as one in your remote file.
A brand new file will only have the Admin and Guest accounts as defaults. You must create a new account.
Ah yes, thanks. :smileyhappy:
I'm getting closer, but am now stuck on something silly... When you first run FMP, you are prompted to enter a username in a dialog. This "courtesy" prompt goes away and is never seen again after that.
However, when I log off my server and let the job run on its own, FMP won't open because it is stuck at this prompt. I believe that the system account that is always running on the box needs to log in and open FMP once so that my scheduled task that runs under the system account is never prompted again.