I could go out to a nice restaurant if I got a dollar for every time I see this issue come up. There are severe limits on what you can export and where you can export it when the script is performed "server side".
I was just reviewing these limitations myself when a server side script wasn't producing the results that I expected just in case I had forgotten a detail.
See This KB article: Import/Export script on FileMaker Server | FileMaker
thats the thing, i stopped this back and have used exactly what the document suggests.
"filewin:" & Get(DocumentsPath) & "Export.csv"
to be honest everything i go to schedule in FM server is a hassle, except backing up databases.
Apologies for not reading your post more carefully.
It might be a permissions issue on the specified folder as the account in force when the server side script runs may not be the same as when you test it client side.
I'd also try it without the "filewin:" text as this "tag" is not normally needed with recent versions of FileMaker when exporting data.
Are you looking in the right place for the output? There is a 'documents' folder in the FMS folder structure. It is not one of the users' documents folders.
cr**, yes hands up , don't i feel like a wolly. Yes it was the documents path on windows I was looking at, I never thought FM server got a different get(docpath) from what PRO did.
Don't tell anyone.. -:)
and different from a USER with access to FMServer. I can login and get my Documents which is wholly different from what FMServer uses, even though I can see what it sees from the correct path!
this one bit me a long time, welcome to the club!