Database Reference
In-Depth Information
Figure 13-2. The Script Debugger window is loaded with information about the current script. You
can see the script's name at the top and all its steps in the middle. The Call Stack at the bottom
shows you the resources that invoked this script. Scripts can be called from buttons, custom menus,
triggers, and other scripts. FileMaker lists the complete history here, showing which called this
one, and below it, the one that called it. If a parameter was passed to any script, then it shows up
down here as well. The Script Debugger window includes a row of unlabeled buttons across the
top. The buttons on the left control the running script. The buttons on the right give you quick ac-
cess to other debugger features.
Controlling Script Execution
Unlike most windows, Script Debugger stays on top of your work, giving you constant feed-
back about running scripts. As long as Script Debugger's window is open, when a script
starts running, it immediately shows up in the Script Debugger, and is essentially paused.
FileMaker is asking you for permission to perform the first step. You control the running
script by using the buttons at the top of the window. Each is described here, shown from left
to right in
Figure 13-2
:
▪ Click
Step Over
to execute the current script step. (FileMaker marks the current step
with a blue arrow along the left edge of the script steps.) FileMaker runs that one step,
