Thank you for your post.
Yes, the Import Records script step using a Bento Data Source is Server compatible.
When you set up the script, select "No dialog", select the Bento Data Source, and then select the Library you want to import. Once that is set, then you can place the file on the server, and each client who accesses the file will be able to import their own Bento database file.
This should work exactly like it would if it were any other file type.
I posted a previous reply but I do not see it, so I'm trying again.
Your response does not address the question.
A "server compatible script step" means that the script step can be run automatically by FileMaker Server, using a schedule.
The Bento import script is listed as server compatible.
With automated server scripts, no client application is involved, and the statement "each client who accesses the file" does not apply.
I only get error 700 if I try this.
Please try doing this yourself and let us know if there are specific instructions to make it work.
Import records is "server compatible" only by the most narrow of margins.
See this knowledge base article for the full story:
Still waiting for an answer to this question.
Your reply including the statement "each client..." is obviously not correct.
There is no client for a server-side script.
Did you read the knowledge base article in the link from my previous post?
Yes. I am not sure why you referred to it though. I do understand what a server side import script does and its limitations.
Did you actually perform a server-scripted Bento import?
In Scriptmaker did you turn on the server-compatibily option and observe that Bento import *is* listed as server compatible.?
The Bento import script step is listed as server compatible in FileMaker.
The link you provided does not mention Bento import. So one or the other is in error and I'm trying to get an authoritative answer on which one.
I guess this hinges on what it means for a script step to be listed as server-compatible and the details of when the "not compatible" message appears.
It was my expectation that if an unsupported-on-server import format was selected, you would get the "not compatible" notice.
My expectation was that it would be exactly similar to what happens if you select import-with-dialog and have the server-compatibility option turned on.
In this case, you DO get the "not compatible" notice.
Quoting from the KB article:
Supporting import/export formats:
Importing/exporting directly to and from another FileMaker Pro file is not supported via a FileMaker Server scheduled script. The supported import/export formats include:
- Comma- Separated Text format (csv or .txt)
- FileMaker Pro HTML Table format (.htm) Export only
- Merge format (.mer)
- Microsoft Excel format (.xls or .xlsx)
- Tab-Separated Text format (.tab or .txt)
- XML format (.xml)
- dBase files (.dbf)
Note that Bento is not listed.
If you read down a little further, you'll also find that the imports can only be performed from one of a few specific locations on the server machine itself (and not from the client's machine.)
I agree that the "compatible" tag in Manage Scripts is mis-leading.
Indeed. The "Server Compatible" can be very misleading.
Once again FMI... Please give us a server side script debugging tool.