When I run a FMP 8 database remotely - that is, when I remotely opening a shared FMP file on a peer-to-peer Filemaker Network - and I run a script that does Save Copy to file:./Backups/foobar.fp7, where is FMP trying to save the file? My computer, or the host computer? And, relative to where?

Not that it saves it -- when I run the script from the client computer I get Error 3 ("command unavailable"), and when I run it on the host computer I get Error 800 ("unable to create file"). Neither of which is helpful to me.

I would have guessed that the file would be saved on the host computer in the Backups folder that resides in the same folder as myDatabase.fp7. (Backups already exists.)

Thanks for any help,

Chap

On a peer to peer setup I thought the host should be able to save copies anywhere on their local hard drive. They can also save to remote volumes if they have a networked drive. I'm guessing that your host computer doesn't have permission to save files to the location that you specified in your script.

As far as I know FM files can't be saved in a Client - Server setup. When using FMServer backups are scripted externally with the Filemaker Server Admin utility, not from within the running FM database. I suppose this is also true for a 'client' in a peer to peer setup (i.e. with both machines runnning FMPro instead of FMServer)

If you use the 'export' script step on a client, the default location will be the folder of the Filemaker application.

Thanks!

You're right; when running on the host, "file:./" refers to the folder containing FilemakerPro.app, instead of the folder containing myDatabase.fp7 as I'd assumed. That's NOT where I wanted to save the copy.

I changed the filespec computation for the backup to:

Get(FilePath) & "/../Backups/" & "myBackup.fp7"

Now I can run the script from the host and it Saves Copy where I want it to.  



However, when I run the script from the client, the filespec is computed as follows:

fmnet:/192.168.1.202/myDatabase/../Backups/myBackup.fp7

Save Copy fails with Error 3 (command not available). I suppose, though, that that's because, as you said, Save Copy isn't available to clients in a peer-to-peer sharing environment.

Thanks for your help.

Chap