Database Reference
In-Depth Information
Figure 13-3. As you step through your script, the debugger constantly updates the last error num-
ber. You can instantly see when an error happened and what the error code is. Best of all, this er-
ror number shows up when error capture is turned on (so you can spot an otherwise silent error)
and when it's turned off (so you can see the code behind the error message). So if you're looking
for error numbers, watch this space. If error capture is turned on, it's the only place you can view
the error condition.
You can even click the error number, which happens to look like a web link, and FileMaker
shows you the help system page that explains each error code.
Pause on Error
If you know your script is producing an error
somewhere
(perhaps because an error message
pops up when you run it), but you don't know where it's coming from, then the “Pause on er-
ror” checkbox is your friend. Just turn this option on and then click Run/Pause. FileMaker
runs the script full speed until any step produces an error.
When that happens, it stops so you can examine your place in the script, see the error num-
ber, and use the debugger controls to manipulate execution. You can also click the Edit Script
button to jump to the trouble spot in the Edit Script window.
