Problem:

The ODBC trace is somewhat difficult to decipher. Are there any other diagnostic capabilities available from OpenESQL?

Resolution:

Yes, you can compile your applicaion with the SQL(TRACELEVEL=n) directive.

Notes :

1. The trace filename is actually OpenESQLTrace.processID.log . If your application is compiled with the SQL(DBMAN=ADO) directive, the trace filename will be ADOTrace.processID.rununitID.log .

2. If the OpenESQL application is executing under the auspices of ASP.NET, the effective user ID under which the application invokes is not your Windows user ID -- instead, the ASPNET user ID -- hence the location of the trace file may not be where you expect it.

3. If you have installed the ESQ08N40.EXE FixPack, or ALL06N40.EXE WrapPack , OpenESQL will write out trace files to the current directory. If the process doesn't have write permissions to the current directory, the trace file will get written to the directory specified by the TEMP environment variable. If that directory is not writable, no OpenESQL trace file will be generated .