The PPJ Framework starting from version 2010 has been instrumented with a granular system of trace calls (we will fine tune it and improve the location and details of the trace calls in future builds and major version releases.)

There are seven trace sources defined in the PPJ Framework:

  1. SQL

  2. Windows

  3. TableWindows

  4. Files

  5. Reports

  6. System

  7. Application

Each source can be set to one of 4 different levels:

  • Off (Default) = 0

  • Error = 1

  • Warning = 2

  • Info = 3

  • Verbose = 4

Enable tracing in {app}.exe.config

To enable tracing in the application's configuration file you can edit it with a text editor or by using our configuration tool. In this case the application needs to be restarted.

Enable Tracing at Runtime

Tracing can be enabled programmatically at any time by simply changing the TraceLevel assigned to the trace source.

For example, to enable SQL tracing at runtime use the following code:

Sys.TraceSQL.Level  = TraceLevel.Info;

Trace Sources

In the following table you can find a description of the kind of activity that is traced for each switch.



SQL operations, including parsing, execution, fetching data, exceptions.


SAL and Windows events.


Table Windows operations, including populating, creating rows, columns, etc.


All files operation and exceptions.


Reporting operations including loading a report, input variables parsing and binding, printing viewing, and errors.


System events, including startup, shutdown, SalCompileAndEvaluare and bind variables resolution and read/write operations, unhandled exceptions, etc.


Application's generated traces.

Last updated