Database Reference
In-Depth Information
This feature also works whether or not error capture is turned on, so it may spot errors you're
already handling. For example, a loop script that moves through a found set of records will
throw an error when you get to the last record. While technically an error, FileMaker needs it
to properly end the loop. When the debugger pauses on one of these, just click Run/Pause
again to run to the next error. Keep going as necessary until you find the error you're looking
for.
TIP
“Pause on error” isn't just a checkbox, it's also the name of an occasional developer conference!
Visit
www.facebook.com/PauseOnError
to learn more.
The Call Stack
The bottom part of the window shows you the call stack.
Call stack
is a nerdy term for the
list of actions that got you to the currently executing script. Every time a script performs an-
other script, it moves down in the list to make room for the new script's information.
FileMaker puts the topmost—and current—script in boldface at the top of the stack. Below
it, you see the script that came before. If that script was itself run by another script,
everything drops one notch to accommodate the most recently called script. You can see how
this looks in
Figure 13-4
. Of course, scripts don't run spontaneously. There has to be some
action that puts things in motion. At the very bottom of a call stack, you can find that action
with an icon to indicate what it is.
Figure 13-5
explains each type.
