Help

Table Of Contents
Using FileMaker Pro Advanced tools
F
ILEMAKER PRO HELP 586
The Call Stack list displays the sub-script.
4. Select a script in the Call Stack list to view that script’s steps in the display area.
Notes
Set Next Step is only available for the currently executing script.
In order to facilitate proper script debugging, the Script Debugger overrides some script
steps. The Allow User Abort script step with the option set to off will not prevent you from
stopping the execution of a script. The Adjust Window script step with the options of hide or
minimize will not hide or minimize the window when encountered through the Step Over or
Step Into buttons.
If a script with access privileges set to Modifiable performs a script with Executable Only
access, the Executable Only script will perform in its entirety without showing its steps in the
Script Debugger. If an Executable Only script performs a script with privileges set to
Modifiable, only the steps in the Modifiable script will appear in the Script Debugger. To edit
a script, choose Authenticate/Deauthenticate Script. For more information about script
privileges and running scripts with full access, see
Editing scripts privileges.
If you open the Data Viewer after choosing Authenticate/Deauthenticate Script, your access
privileges are maintained in both the Data Viewer and Script Debugger until you close the Script
Debugger.
You can open one Edit Script dialog box per script.
You can debug a startup script by opening the Script Debugger before opening your
database file.
When you close the Script Debugger while a script is paused, the script resumes and
completes.
When a File Open script is loaded, the Script Debugger displays OnFirstWindowOpen.
When a File Close script is loaded, the Script Debugger displays OnLastWindowClose.
When you debug a script that is called from a button, the button is identified in the Call
Stack list by the filename and layout in which the button is located. The button name is the
button object name that was assigned using the
Inspector. If no name was assigned in the
Inspector, <unnamed button> followed by the filename and layout appears in the list.
When the Script Debugger stops on a script step called by a button in the script step list, the text
above the list changes to Button: <name of button>, or it changes to Button: <unnamed
button> if no name was assigned in the Inspector.
When you debug a script that is called from a custom menu, the menu item is identified in
the Call Stack list by menu item name and filename. When the Script Debugger stops on a
script step called by a custom menu in the script step list, the text above the list changes to
Menu item: <custom menu item text>.
Related topics
Creating and editing scripts
Using the Data Viewer (FileMaker Pro Advanced)
Disabling script steps (FileMaker Pro Advanced)
You can disable and enable script steps to test portions of a script. When you run a script, disabled
script steps are skipped.