Hi Chris,

Thank you for response..

1) If your App would like to track the SQL, you can use the Transaction Object's SQLPREVIEW event (aka SQLCA) to record your App's DB activity.

  --> I am using sybase, so added as "TRACE SYC" to capture SQL logs

2) You can record your App's event execution though by using the EXE tracing option. For example: <YourApp.exe?  /pbdebug

   Then read the log output to review the various event execution.

Note that you can also use the Application Profiler feature of PB as well to trace Event execution within your PB App from the IDE. You can also embed this into your production deployed App's via the TraceXxxx() commands.

  --> Can I get any examples to records event execution and also for exception handling

Hi Tamilselvan;

  The data base log that you are referring to via the DBTRACE setting is not a DB Log but an SQL Tracing log of what is sent by your PB App and what the DBMS returns back to your App. The DB Log is something that the DBMS server maintains within its address space.

  If your App would like to track the SQL, you can use the Transaction Object's SQLPREVIEW event (aka SQLCA) to record your App's DB activity.

  For the Event Log, I assume that you are referring to the MS-Windows Event log. You can write to this log (via SDK calls) but you cannot read or intercept applications writing to the O/S event log.

  You can record your App's event execution though by using the EXE tracing option. For example: <YourApp.exe?  /pbdebug

   Then read the log output to review the various event execution.

Note that you can also use the Application Profiler feature of PB as well to trace Event execution within your PB App from the IDE. You can also embed this into your production deployed App's via the TraceXxxx() commands.

HTH

Regards ... Chris