![]() |
Next Page |
| Contents > Creating scripts to automate tasks > Importing scripts from other FileMaker files |
|
|
| Importing scripts from other FileMaker files |
| FileMaker Pro allows you to import scripts from other FileMaker files. You can also copy and paste scripts between files. See Copying and pasting scripts. |
| When you import a script, FileMaker Pro attempts to map fields, layouts, tables (including those used in relationships), and so on based on their names. Fields and layouts are mapped using their fully qualified names, and these must match exactly or the reference will not be imported. If the referenced object cannot be found, FileMaker Pro flags it as missing. After importing a script you should edit the script to make sure that all references are valid and appear as intended. |
| Important Always review your imported script before performing it for the first time. |
| To import a script: |
| 1. | Open the file into which the script will be imported. |
| 2. | Choose Scripts menu > ScriptMaker. Or, choose File menu > Manage > Scripts. |
| 3. | In the Manage Scripts dialog box, click Import. |
| 4. | Open the file that contains the script(s) you want to import. |
| 5. | In the Import Scripts dialog box, select the script(s) you want to import. |
|
|
If one or more of the scripts you're importing refer to other scripts, make sure you select and import all the referenced scripts at the same time. For more information, see the Notes below. |
| 6. | Click OK. |
|
|
The Import Summary dialog box appears. |
| 7. | Click Open Log File to view the import log file, or click OK to close the Import Summary dialog box. |
|
|
If FileMaker Pro reports errors, follow the steps in Creating and editing scripts using ScriptMaker to correct the <unknown> references in each script. During the script import, FileMaker Pro checks all references to fields, layouts, other scripts, files, and so on, in each imported script. References must match exactly to be included in the import. If a referenced object is not found, FileMaker Pro flags it as <unknown>. |
| 8. | Close the Manage Scripts dialog box. |
| Tip You can import scripts into a group by selecting the group, then clicking Import. |
| Notes |
| The match for field names is not case-sensitive. |
| When importing a script that references a related field, the fully qualified fields names must match identically, including the names of the tables as they appear in the relationships graph. |
| When importing script steps that contain more complex information (for example, find requests, sort order, import field order, and export field order, etc.), FileMaker Pro discards any missing field references. |
| To import a script, you must have access privileges in the source file that allow you to modify the script. |
| The option Run script with full access privileges is only imported when the user performing the import has logged into the target database with full access privileges. |
| Related topics |
| Managing groups of scripts |
| Deleting a script |
| Planning a script |
|
|
| Contents > Creating scripts to automate tasks > Importing scripts from other FileMaker files | Next Page |