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.
Many scripts refer to files, fields, layouts, records, and other scripts. In addition, some script steps, such as Set Field, Insert Calculated Result, Replace Field Contents, and so on, may have field references embedded in calculations. While these references may be valid in the original file, it is possible that they will be invalid in the file into which they are being imported.
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.
|
2.
|
.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.
|
|
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 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>.
|
•
|
When importing a script that references a related field, the fully qualified field names must match identically, including the names of the tables as they appear in the relationships graph.
|
|
•
|
When importing script steps that contain calculations (for example, If, Set Field, and, Insert Calculated Result), if FileMaker Pro cannot match all items referenced in the calculation (i.e. tables, fields, or custom functions), the calculation is commented out (using ‘C’ style comments).
|
|
•
|
When importing scripts from single table files, you can avoid most of these naming errors by making a copy of the file containing the script you want to import. In the copied file, rename the table to match one of the tables in your destination file, and import the script from the copy. Script steps that refer to identically named fields and layouts in both files will import properly because the underlying table in the source file has the same name as a table in the target file.
|
|
•
|
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.
|
|
•
|
|
•
|
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.
|