Macros and Errors
 Sometimes information is not kept.
──────────────────────────────────────────────────────────────────────────────

 It has been known for the debugging information to be lost when running
 macros. If your program should fall whilst it is executing a macro,
 debugging information may be lost about the macro.

 This is not a fault of the debugger.

 If this situation should arise, then the debugger will place you on the
 calling module (the previous one in the stack).

 You may see the source code that cause the problem by chaning to the stack
 window <Alt-4> and moving the highlight bar to the correct module. This will
 show you the source code that the problem occured in and the cursor will be
 on the line of code that caused the problem.