Consider the following when setting breakpoints based on errors:
For any breakpoint triggered by an error, an alert box appears stating "Stopped due to Break on error nnnnn." (the error number appears for all three types). The Debugger gains control at the next executable line following the line of ABL code that caused the error.
Note: For On Error, the Debugger validates that you entered a number from 1–99999, but otherwise does not verify that an error corresponding to the number exists.
Errors that occur in hidden procedures do not trigger error breakpoints. Hidden procedures are procedures whose filename begins with an underscore (_). For more information about hidden procedures, see Hiddenprocedure files .
If your program does not trap a stop condition (with ON STOP, for example), the Debugger ignores the error that causes the interruption, since the program terminates. Similarly, the Debugger ignores an error condition that is not trapped (with ON ERROR, for example) and results in program termination.
For any breakpoint triggered by an error, an alert box appears stating "Stopped due to Break on error nnnnn." (the error number appears for all three types). The Debugger gains control at the next executable line following the line of ABL code that caused the error.