Allow User Abort script step

Contents > Script steps reference (alphabetical list) > Control script steps > Allow User Abort script step

Allow User Abort script step

Format


Allow User Abort [<on or off>]

Options

On to allow users to stop a script by pressing Esc or ⌘-.(period) (Mac OS).

Off to prevent users from stopping a script by pressing Esc or ⌘-.(period) (Mac OS).

Web compatibility

This script step is web-compatible.

Description

By default, Allow User Abort is turned on for an entire script. In other words, users can stop a script by pressing Esc or ⌘-.(period) (Mac OS). To prevent users from stopping a script, use the Allow User Abort script step and set it to Off. FileMaker Pro automatically turns Allow User Abort on after the script finishes running.

Example

To set up a kiosk solution, use:


Allow User Abort[Off]

Then, create the rest of the script as a looping script that never ends. Use the Allow User Abort script step as the first step to prevent people from closing the file or exiting the application.

The next script steps display a "welcome" screen for three seconds when the database is opened, then continues to a data entry layout. The user cannot cancel this "welcome" screen display.


Allow User Abort [Off]
Go to Layout ["Welcome"]
Pause/Resume Script [Duration (seconds): 3]
Go to Layout ["Data Entry"]
Allow User Abort[On]

The following script verifies that all records have client numbers entered, audibly notifies the user when it finds a missing number, and waits so the user can enter the number. This script runs when the database closes and can't be cancelled by the user.


Allow User Abort[Off]
Go to Record/Request/Page[First]
Loop
   If[IsEmpty(Table1::clientNumberField)]
      Speak["Client number is missing"]
      Pause/Resume Script [Indefinitely]
End If
   Go to Record/Request/Page [Exit after last; Next]
End Loop
Allow User Abort[On]

Script step categories

Contents > Script steps reference (alphabetical list) > Control script steps > Allow User Abort script step