FMS is not a FMP client. One FMS cannot talk to another FMS. Your FMSA cannot run script in the files in FMS because it cannot connect to them.
"My theory is that all of Scottish cuisine is based on a dare." --- Mike Myers
Here is another one for you.
A wee three script steps.
Go to Layout [ “Maintenance - Inventory” (INVENTORY) ]
Set Variable [ $Input; Value:Get ( DocumentsPath ) & "IPAD.FILEMAKER.txt" ]
Import Records [ Source: “$Input” OR “filemac:/TriloBYTE/Users/stephen/Desktop/IPAD.FILEMAKER.txt”; Target: “INVENTORY”; Method: Update matching; Character Set: “Mac Roman”;
All steps are server compatible. This throws an error 100 when run serverside.
It has been suggested that I use $$Globals instead. G'Day Kiwi!
Hi Stephen: One of our engineers chimed in with this...
Error 100 is file missing, and is occurring because Get ( DocumentsPath ) is restricted on Server. FileMaker Help for the function says:
When running on FileMaker Server, Get(DocumentsPath) returns the location of the Documents folder, which is in the same folder as the server's Backups, Databases, and Scripts folders. The Documents folder is used as a shared location that scripts from different sessions or other processes on the machine can use to import or export files.
Thanks very much. Nothing quite like being reminded about something I apparently had filed away, had learned at Devcon, have it in my Server 12 session notes.
Time for a full scale Uitwaaien.
Uitwaaien (Dutch): - To walk in the wind, but in the more figurative (and commonly used) sense, it means to take a brief break in the country side to clear one’s head.