I am trying to get a server compatible script to export a found set to a csv file on my server.

I understand from previous posts that when using Server 9 , the location of the exported file has to be very specific.

This is what I have so far after the initial find has been scripted

Set Variable [$filepath; Value:"filewin:" & Get(DocumentsPath) & "exportfile.csv"]

Export Records [No dialog; "$filepath" ; Windows (ANSI)]

When the Script runs on the server , i get the status "ScriptMaker script aborted"

where am i going wrong.

I also just tried using

Export Records [No dialog; "filewin:/C:/Program Files/Filemaker/Filemaker Server/Data/Documents/exportfile.csv" ; Windows (ANSI)]

but this doesn't work either

any help would be greatly appreciated

Edited December 15, 200916 yr by Guest

i get the status "ScriptMaker script aborted"

There may be other reasons for the script to abort - not just bad filepath (which I doubt). Does the script have the correct privileges to export?

yes, I believe so.

Can you confirm that export is possible using FM Server 9.

The reason I ask is , my client machine is running FM 10 Advanced and when I am in the script menu and have show compatibility set to 'Server' nothing is greyed out , indicating that everything is fine - but is it assuming I am running FM Server 10 and therefore the Export Records (no dialog) is no problem?

thanks

Aha..

The Server compatibility options only became available with FM10 - which also require FM SERVER 10.

FMS 9 relies upon the previous web compatible steps - but noticeably the EXPORT records step only became server compatible with FM10 - you will need to upgrade to FMS 10

ok , thanks.

The way I have solved the problem is to use 360works RemoteScripter to get my Server to trigger my client machine to run a script to save the csv files to the servers hard drive. Then I used 360works FTPeek plugin to run a scheduled script to ftp the files a few minutes later to my webspace.