Script Steps Reference

Miscellaneous script steps
F
ILEMAKER SCRIPT STEPS REFERENCE 241
Originated in
FileMaker Pro 6.0 or earlier
Description
The custom message dialog box can take user input for up to three fields in the database, and
display data from up to three fields in the database. The script pauses as long as the custom dialog
box stays on the screen. Fields used for input can be of type text, number, date, time, timestamp, or
container. Your custom dialog box can also have up to three buttons, with custom button titles.
Use the Get(LastMessageChoice) function to determine which button the user presses.
• 1 for the first button (by default, labeled OK)
• 2 for the second button (by default, labeled Cancel)
• 3 for the third button
Notes
• If values entered into input fields don’t match the field type, a validation error message
displays. The user must resolve validation errors before the dialog box can be closed. See
Defining field validation for more information.
• The fields you specify don’t need to appear on the current layout. Show Custom Dialog
input fields are independent of layouts, similar to the Set Field script step.
• Data can't be inserted into calculation or summary fields.
• Show Custom Dialog ignores any field entry options. See Allowing or preventing entry into
fields for more information.
• Data entry via the Show Custom Dialog script step is limited by any access privileges
criteria that may be in place. (To enable the script for all users, right-click the current script in
the scripts pane and choose Grant Full Access Privileges.)
• (Windows) You can create a keyboard shortcut for a custom dialog box button by placing an
ampersand before the shortcut key letter in the button label. For example, to create a
keyboard shortcut ‘D’ (Alt+D) for a button labeled ‘Done’, type the label ‘&Done’.
• For databases created with pre-12 versions of FileMaker Pro that are opened with
FileMaker
Pro 14, the Commit Data checkbox for Default Button is selected when you
open the Show Custom Dialog dialog box.
• Before you change the data commitment status of a button for a database that’s already in
use, consider the behavior that users currently expect of the button and how changing its
behavior could affect the validity of data committed (or not committed) to the database.
• To develop more-complex custom dialog boxes, you can use the New Window script step.
Example 1
Performs a find. If no records were found, displays a custom dialog.
Perform Find [Restore]
If [Get (FoundCount) = 0]
Show Custom Dialog ["No records were found."]
End If