Script Steps Reference
Table Of Contents
- Script steps reference (alphabetical list)
- About script steps
- Control script steps
- Navigation script steps
- Editing script steps
- Fields script steps
- Set Field
- Set Field By Name
- Set Next Serial Value
- Insert Text
- Insert Calculated Result
- Insert From Device
- Insert From Index
- Insert From Last Visited
- Insert From URL
- Insert Current Date
- Insert Current Time
- Insert Current User Name
- Insert Picture
- Insert Audio/Video
- Insert PDF
- Insert File
- Replace Field Contents
- Relookup Field Contents
- Export Field Contents
- Records script steps
- New Record/Request
- Duplicate Record/Request
- Delete Record/Request
- Delete Portal Row
- Delete All Records
- Open Record/Request
- Revert Record/Request
- Commit Records/Requests
- Copy Record/Request
- Copy All Records/Requests
- Import Records
- Export Records
- Save Records As Excel
- Save Records As PDF
- Save Records As Snapshot Link
- Truncate Table
- Found Sets script steps
- Windows script steps
- Files script steps
- Accounts script steps
- Spelling script steps
- Open Menu Item script steps
- Miscellaneous script steps
- Show Custom Dialog
- Allow Formatting Bar
- Refresh Object
- Beep
- Speak (OS X)
- Dial Phone
- Install Plug-In File
- Install Menu Set
- Set Web Viewer
- Open URL
- Send Mail
- AVPlayer Play
- AVPlayer Set Playback State
- AVPlayer Set Options
- Refresh Portal
- Send DDE Execute (Windows)
- Perform AppleScript (OS X)
- Execute SQL
- Send Event
- Comment
- Flush Cache to Disk
- Exit Application
- Get Directory
- Enable Touch Keyboard
- Glossary
Miscellaneous script steps
F
ILEMAKER PRO SCRIPT STEPS REFERENCE 271
Notes
• SQL statements are limited to a maximum length of 256 K characters (512 KB).
• FileMaker Server, FileMaker WebDirect, and Custom Web Publishing support this script
only if the With dialog option is set to Off.
• If you use the Execute SQL script step to send ODBC data that contains Unicode strings,
your ODBC driver must support Unicode. Otherwise, the results may be inconsistent.
• ODBC import, the Execute SQL script step, and external SQL data sources are not
supported in runtime solutions created with FileMaker
Pro Advanced.
• Because Microsoft SQL Server supports both Unicode and non-Unicode field types, you
must prefix all Unicode strings with an uppercase “N” (which stands for “National” in the
SQL-92 standard). Otherwise, when a Unicode string containing non-English characters is
passed to Microsoft SQL Server, you may lose any data that doesn’t exist in the Microsoft
SQL Server code page.
Example 1
Updates records in the Employees table of an external ODBC data source.
Execute SQL [With dialog: On; SQL Text: INSERT INTO Employees (EmployeeID,
FirstName, LastName, Title, WorkPhone, Salary) VALUES (100, N'Joe',
N'Smith', N'Software Engineer', '987-7000', 100000) UPDATE Employees SET
Title = N'Manager' WHERE EmployeeID = 103 DELETE FROM Employees WHERE
EmployeeID = 103]
Example 2
Calculates and performs an SQL statement to update records in the Customers table of an external
ODBC data source.
Execute SQL [With dialog: On; Calculated SQL Text: "INSERT INTO Customers
(Company, LastName) VALUES (" & Customers::Company & "," & "N'" &
Customers::Last & "')"]