4D v13
Tracing and debugging
- Self-training
-
- Fundamentals
- Introduction
- First steps in 4D
- Presentation of the final database
- Forms and buttons
- Display at startup
- Menu bars
- Page 0 and page 1
- Form and navigation pages
- Tables, fields
- Relations
- Entry, deletion
- Importing
- Output forms
- Queries and sorts
- Quick reports - exports
- Query by formula, applying a formula
- Form inheritance
- Printing forms
- Handling form objects
- Object properties
- Calculations and formulas
- Overview of variables
- Tracing and debugging
- Generic programming (without pointers)
- Pointers
- Events
- Arrays, pop-ups, list boxes
- Windows and navigation
- Triggers
- Current selection
- Sets and named selections
- Processes
- XLIFF and translation
- 4DWrite Plugin
- Switching to client/server mode
- SQL
- BLOBs
- Components
- SVG
- Web Server
- Download
Tracing and debugging
In addition to the manipulations explained in the video, you should also note that:
4D can run interpreted and compiled databases.
In all cases, we recommend that you check the syntax of your development projects using the compiler.
Note: tracing is only available with interpreted databases. Obviously, in a compiled/merged database, we do not have access to the source code. Only users referenced as developers (belonging to a group that has access to the Design environment) can enable tracing.
In addition, the debugger also lets you:
- modify data in fields and variables being executed
- add temporary break points, conditional break points, and so on
- run code (Warning: this is risky!)
- display table and field numbers
- remove all displayed expressions
- choose the information to be shown in each area of the editor
- and so on.
Most of the things mentioned above can be accomplished using the context menu (right click)
When using the TRACE command in the code, you can stop "tracing" using the NO TRACE command.
A break point is a red dot that you place by clicking in the row number column next to the row where you want 4D to start tracing. It is linked with the row where it is placed.
You can condition break points (ALT-click when creating a break point or on one that already exists). Conditioning is done by formula or depending on a certain number of passes.
Break points can also be temporarily disabled.
You can use the Runtime explorer to remove break points placed in the code without actually returning to the method concerned.
Product: 4D
Theme: Tracing and debugging
