Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 5926 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I've a script to export records from a hosted database. The question is I want that script to run automatically by itself at night, so I want to store the exported file on the same server where FMS is running.

I don't know how to specify the export path. If I specify the same as the database containing the script I get the following error:

"filename.fp7" could not be created on this disk. Use a different name, make more room on the disk, unlock it or use a different disk.

I just have been able to export into the client machine...

Btw: I am in a Windows XP pro LAN.

Any idea?

Thanks in advance

Posted

I've a script to export records from a hosted database. The question is I want that script to run automatically by itself at night, so I want to store the exported file on the same server where FMS is running.

FileMaker Server 9 does not support server side scripts with export script steps. This would need to be done client side, and you wouldbe much better off keeping the exported files on a fileserver in a dedicated directory rather than on the FileMaker Server machine.

Steven

Posted

Thanks Steven. I see that only web compatible script steps are supported on server side ScriptMaker scripts.

Posted

The purpose of the export is to have a snapshot of a certain table at a precise time.

I use fp7 file format.

I know I could simply schedule a backup but the backup scheduler doesn't allow me enough precision.

Thanks for your reply.

This topic is 5926 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.