![]() ![]() Use the Get(LastError) function in server-side scripts to handle error conditions. Server-side scripts can’t cause a client to display FileMaker alert messages as when scripts are run on clients, so server-side scripts always perform as if the Set Error Capture script step were set to On.Scripts run by a schedule use the account specified in the schedule. Scripts run by Perform Script On Server use the same account as the client.Server-side scripts can use the Perform Script script step to perform sub-scripts, which also run on the server, only if those sub-scripts are in files on the same server and are already opened by the client.Therefore, the OnFirstWindowOpen script trigger is activated when the script starts and the OnLastWindowClose script trigger is activated when the script ends. Running server-side scripts opens and closes the files that contain the scripts.If records are locked by a client, server-side scripts cannot access uncommitted data or change the contents of those records.to use the Import Records or Execute SQL script steps with an ODBC data source that uses the server’s DSN Notes.to enable FileMaker Go clients to perform tasks that require plug-ins, which are supported on FileMaker Server and FileMaker Cloud but not in FileMaker Go.to offload long-running tasks from slower clients to a faster server.to improve performance by reducing the amount of network traffic between the client and server.You can also refer to the Compatibility table for each script step in Script steps reference. Script steps that aren’t supported appear in a different color. To see which script steps are supported by the FMSE, in the Script Workspace in FileMaker Pro Advanced, open a script, click, then select Server. # Continue with script steps supported by the FMSE the Get(ApplicationVersion) function before other steps in order to check whether the script is running on FileMaker Server or FileMaker Cloud, then perform only supported steps.For example, the Open File script step is unsupported by the FMSE, so the following script running on the server will skip that step and return "unsupported" in the result. the Get(LastError) function after a step in order to check whether that step is unsupported, then perform supported steps instead.To handle unsupported steps, your script can use the If script step with: However, attempting to perform an unsupported script step returns error 3 ("Command is unavailable"), skips the unsupported step, and continues to the next step. ![]() Many script steps are supported by the FMSE. A schedule can be set to end if the running script exceeds the specified time limit.A client using the Perform Script On Server script step has the option to wait for the script to complete on the server and use the Get(ScriptResult) function to capture the result.Server-side scripts run the same way regardless of how they’re started, except for the following: Filemaker cloud vs filemaker server password#the files were already opened by the client that started the server-side script, or set up with an account name and password specified in the file’s File Options dialog box.can access other FileMaker Pro Advanced files only when both of the following are true:. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |