Saving a screenshot as a reference on a remote server

[davidnickerson]

I have a client who wants to be able to store screenshots in container fields in an existing database hosted by FM Server.

 

Ideally, I'd like to script the process so the following occurs:

 

1. Client saves screenshot to clipboard in OS, then clicks into container field.

2. Container field is a script button

3. Script does the following:

 

a. navigates to an image storage folder located on the server.  if the proper folder (based on record number) does not yet exist, one would be created.

 

b. exports the original screenshot image to the folder

 

c. imports the screenshot back into the container field as a reference

 

Since the client does not have the server volume mounted on their desktop, I'm having trouble figuring out how to access the server volume as a path in the script.

 

Thanks in advance for assistance with this!

[Matthew F]

Someone may correct me on this, but I thought that scripts run by the client only have access to the local file system.  Server-side scripts (scheduled by the Filemaker Server Admin client) save files on the server file system. 

[Wim Decorte]

Someone may correct me on this, but I thought that scripts run by the client only have access to the local file system.  Server-side scripts (scheduled by the Filemaker Server Admin client) save files on the server file system. 

 

No, scripts run by an FMP client have the same rights as the user that has FMP open, that means access to any and all network shares.

 

FMS only has local system rights by default so server-side schedules can not reach out across the network, unless you 

:

- change the FMS permissions

- or use OS-level scripts and run them with the proper account that has proper access to where you want to do stuff

Since the client does not have the server volume mounted on their desktop, I'm having trouble figuring out how to access the server volume as a path in the script.

 

This can only be done by using OS-level scripting (or perhaps some plugins).  The volume needs to be mounted (if this is OSX), and the users need to have proper read and write privileges to the shared folder.

 

DO NOT under any circumstances share a folder that contains live FMS files or its backups.