When encountering errors in code, it is no longer necessary to exit the Trace Debugger, make code changes, and launch the debugger again. With the Trace Prompt toolbar and line jumping, command corrections may be made and code may be executed repeatedly.
For example, if a missing variable error occurs , e.g. "Column or variable vCustID not found." on line 52, and debugging stops, do not close the Trace Debugger. Instead, perform the following:
1.Use the Jump to Line feature [F11] to jump to line 51 (or a lesser line number containing code).
2.Within the T> Prompt input console, enter: SET VARIABLE vCustID INTEGER
3.Then, continue stepping through the code with the [F10] key.
The error should not appear and debugging may continue.
If the code is expecting a different data type, the above steps may be repeated, and the SET VARIABLE command can be adjusted.
Line jump may also be used to start debugging at a specific line number, and to skip over one or many commands.
