#Filemaker server script drivers
#Filemaker server script archive

For a script that runs on the server, only 64-bit ODBC drivers are supported. If you run a FileMaker script that uses the import ODBC script with a third-party ODBC driver, you need to use the 64-bit version of the ODBC driver. See Viewing and downloading log files.įor server-side FileMaker scripts, the Get(AccountName) function initially returns the account name that the script was run under (specified when the schedule is created). FileMaker Server can run system-level script files, such as a Windows batch command, VBScript, or OS X shell script (bash, Perl, Python). The Event.log file contains detailed information about errors or script steps that are skipped when FileMaker Server runs FileMaker scripts.

Some script steps have options that are skipped, such as an option to show a dialog box. See Disconnecting clients from FileMaker Server.

If you do not select this option and a FileMaker script stops responding, you can stop the script on the Databases page by stopping the script shown in the clients list. You can select End the schedule if the timeout is reached to stop the FileMaker script schedule if the script takes longer to run than the specified time limit, or if the Database Server stops. See Hosting databasesįor information about creating FileMaker scripts with script steps that are supported in a FileMaker Server script schedule, and how server-side scripts run, see FileMaker Pro Help. The script schedule you create to run the script must be on the same FileMaker Server deployment as the hosted database file. The script must be defined in a database file that is hosted on FileMaker Server. The script should include only script steps that are supported in a FileMaker Server script schedule. To run a FileMaker script on FileMaker Server: such as starting a Selenium server for testing in a browser. You use the Script Workspace in FileMaker Pro to build scripts by selecting from a list of FileMaker Pro commands, called script steps, and specifying options. Perhaps there is a script that they should run or some environment variables that they need. Remove duplicate records before a scheduled backup Search: Filemaker Pro Conditional Value List Example.

#Filemaker server script archive

Process and archive new transactions nightly Perform a field recalculation across all records The reporting routine optionally uses PSOS, so you can dive in painlessly and see what you’ve been missing. PSOS, host the demo files on FileMaker Server 13 or later. (Also, if you’ve been putting off exploring Perform Script On Server, a.k.a. FileMaker scripts that run on FileMaker Server can do simple or complex tasks such as: Bottom line: each of these three techniques can be fastest, depending on circumstances. You create a schedule to run a FileMaker script schedule, specify the database and the FileMaker account to use to run the script, choose a script created in the database, and specify when to run the script. FileMaker Server can run FileMaker scripts that are created in hosted databases.