I have inherited a database that I've moved from FM 12 to FM 16. When opening a file with sensitive information, there's a script that calls Re-login to authenticate permitted users. When this script runs from FM Server 16, it pauses and then completes without even opening the Dialog box. Using the script debugger, the Re-login call is returning error 1 - User Canceled Action. When I run the database locally, without the server, everything works fine. Any ideas?
Thanks!
Mike, thanks for your reply. I'm on a steep learning curve here! Reading about scripts on the server, I found the following that suggests that, by default, scripts run on the client. So that would suggest that this isn't my problem? What I don't understand about my error is why I'm getting a "User Canceled Action" error...
About running scripts on FileMaker Server
Scripts in files hosted by FileMaker Server normally run on the client. However, you can run a script on the server (a server-side script) by using:
•a Perform Script On Server script step in a script running on a client
•a FileMaker Server schedule (see FileMaker Server Help)
We might need to define some terminology here.
When this script runs from FM Server 16
To me, that implies a script running as a scheduled script on FMS or Perform Script On Server from the client. Do you mean you only get this issue when the file is hosted on the server (but the script is run on the client), as opposed to a local file on the client computer?
Yes, my mistake - this error only happens when the file is hosted on the server and the script is run on the client. When I open the file locally (through the network) directly on my local computer, there is no problem. This is FM 16 on a Mac, and FM 16 Server on a Mac as well.
Thanks for taking the time to help me sort this out!
Always start with the documentation:
Re-Login - FileMaker Pro 16 Help
Note that the documentation states support for FileMaker Server is "partial", and that points to these comments:
So, based on that, is your script step running with the "with dialog" checkbox off?
If it's not, then that means nobody is there to log in, and you haven't hardcoded any credentials for the server to use in lieu of that automatically, so it fails.
You have two options, either hardcode credentials, or detect that this script is running as a server script and either hardcode credentials or skip it entirely.
That's easy to script: