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

importing TableA to TableB in same database during Scheduled script gets error 100


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

Recommended Posts

Posted

Hello,

I have a script in database "A" that imports from Table_Remote to Table_Local in database A (it imports from itself.) Table1 is a remote table from Database "B", both hosted on the same FMP Server 10.

When I run the script manually via the fileMaker app it imports fine. When I run it as a script step I get error 100 (File is Missing) at the import step. It doesn't seem to have issues opening database B to access Table_Remote because I can export data from that table within in the script, it just can't find itself to import.

Does anyone know what I need to do to allow it to import from itself during a scheduled Script? I really have no idea why it's not working.

In case you're wondering, I'm doing a search on Table_Remote and then importing only one field from the search result to Table_Local. Otherwise I would just import directly from Database B.

Does anyone have any Idea why this isn't working? I will be your best friend if you can help!

Thanks!

Posted

I believe FMS can only import from files (even FM files) that are in the Get (DocumentsPath) and Get(TemporaryPath).

  • 2 months later...
Posted

Per the FM Knowledge Base article "Import/Export Script on FileMaker Server 10"

FileMaker Server can only import from and Export to the following locations:

* When using the Import Records script step or Export Records script step in a FileMaker Server scheduled script, keep the following in mind:

*

o Any specified file must in the Documents folder, the temporary folder, or a child folder of either the Documents folder or the temporary folder. For example, the following are all valid paths for file.csv:

/file.csv

/file.csv

/Folder1/file.csv

/Folder1/Folder2/Folder3/Folder4/file.csv

o Any path specified that isn’t a complete path to the file (for example, anything other than/Library/FileMaker Server/Data/Documents/<0 or more directories>/ ) is evaluated as being relative to the temporary path.

o Any paths that include “..” are considered invalid.

Is it just me or that this render the ability run Server Side import/export scripts nearly useless?

This topic is 5532 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.