Andrew,
I was as confused as you by the knowledge base article you quote. I
found that files would import if they were in this directory:
/Library/FileMaker Server/Data/Documents/
I'm running OS X, but I think the important point is that the files need
to be within the path of the FileMaker Server or the path in which
FileMaker Server expects to find its files. In order to be imported the
files in my directory need to be copied using a shell script from a
directory (similar to your NetworkResources directory) that FileMaker
Server is unable to access.
Michael Larson
L&S Computing Resources
UC Berkeley
On 12/15/09 8:51 AM, Andrew Kappy wrote:
FMSA 10, FMPA 10
I have an import script that is well tested on both Mac and Windows
clients. When run as a server side script the import fails with script
error 100.
My import is for an XML file. My setup includes a path such as:
filewin://NetworkResource/Folder1/Folder2/Folder3/Folder4/$$file
Any suggestions?
BTW
There is a knowledgebase article (7035) which is less than helpful as I
don't know what limitiations are included in "Temporary Path":
"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:
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:
<Documents>/file.csv
<Temporary Path>/file.csv
<Documents>/Folder1/file.csv
<Temporary Path>/Folder1/Folder2/Folder3/Folder4/file.csv
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>/<filename> ) is evaluated as being relative to the
temporary path.
Any paths that include “..” are considered invalid."
-----------------------------------------
Andrew Kappy
