Breakpoints allow you to make the debugger stop in the macro code under certain circumstances :
•When a given code line is reached.
•When a variable reaches a certain value.
•A combination of both of the above.
The list of breakpoints is displayed at the bottom right of the debugger.
Each breakpoint appears in the list of breakpoints with its condition, if any, and the code line it refers to, if any. In the example above :
•The first breakpoint is set to always break when execution reaches line 12.
•The second breakpoint is set to break on line 7 whenever the value of the variable n_GridPage equals 2.
•The third breakpoint is set to break the very first time the value of n_OutputPage reaches 18 (and thereafter).
This variety of breaking options (which we will discuss in the next section) is very useful to break selectively, since you usually only invoke the debugger for specific cases, possibly on specific pages and dates. The use of breakpoint to check the overall logic of the macro is best done at design-time in the Macros Editor when testing macros.