The interactive Trace Debugger works with external files including ASCII command files, application files (.rba), external forms, or application files encrypted with CodeLock. With CodeLocked files, the source files must be located in the same folder as the CodeLocked files. If you are going to Trace a CodeLocked application, then you must also follow the same R:BASE standard of (.APP) for the source files, and (.APX) for the CodeLocked files.
The Trace Debugger also debugs internal code stored within the database as Entry/Exit Procedures (EEPs) and actions within forms, reports, and labels, stored procedures, and code stored in tables (RUN SELECT).
Certain commands used in applications require keyboard input as the Trace Debugger processes them. You cannot return to the Trace Debugger when the system is processing the input. You must first exit the form, menu, dialog, or edit screen.
Here is a list of commands that require user input:
•BROWSE
•CHOOSE
•DIALOG
•EDIT
•EDIT USING
•ENTER
•FILLIN
•GATEWAY
•LBLPRINT
•PAUSE
•QUERY
•RBEDIT
•REFF
•RUNRBA
The Trace Debugger is interrupted if an error or warning occurs while processing commands. This halt in debug processing occurs and the error or warning message is displayed regardless of the Error Messages and Status Messages settings.
The error or warning message displayed relates to the last command processed. This is the command on the highlighted line in the Trace Debugger window.
The Trace Debugger exits when the command file finishes. To exit sooner, press the "Stop Script Debugging" button on the Trace Toolbar, the [Ctrl+F2] hot key combination, or the "x" on the main Trace Debugger window.
