Complete the fields on the Tracing tab to aid in troubleshooting. AcuODBC provides you with three different ways to trace activity:
Naming Trace Files
By default, the log files are place in the directory represented by the value of the %TEMP% or %TMP% environment variable. The "%d" represents the thread ID. This is used so that different connections do not interfere with each other.
If you wish to use names other than these defaults, note the following:
You can use two types of escape sequences in the names of trace files.
You can enter either %TEMP% or %TMP% as the first characters in the name of the trace file. This sequence of characters is replaced by the value of the TEMP or TMP (respectively) environment (not configuration) variable. This is allowed only as the first set of characters in the file name, and is ignored if it appears elsewhere in the name of the file. The values of the environment variables are replaced exactly. Verify that there is a correct directory separator, either at the end of the environment variable or in the name of the trace file. For example:
TEMP=C:\Winnt\Temp Driver Trace File: %TEMP%\acuodbc_trace_log
resolves to "C:\Winnt\Temp\acuodbc_trace_log".
You can use a single "%d" in the filename (such as "vision_trace%d.log", "acuodbc_trace%d.log", or "sql_trace%d.log"). If the filename contains only one "%d", those characters are replaced by the thread ID so that different connections do not interfere with each other. If "%d" is not part of the filename, or if the filename contains more than one "%d", no translation is done. One exception exists to this rule: if "%%" (two consecutive % signs) is part of the filename, the "%%" is replaced by a single "%". (If the filename is $sql_trace%d.log%, for example, no translation is done.) If your application makes multiple connections to the AcuODBC driver, and you send tracing to a file without this sequence, the trace file most likely will not be usable, because the different connections overwrite each other's information.
Vision Tracing
The Vision trace file lists all the Vision file operations attempted by AcuODBC, such as file opens, reads, writes, etc.
This field lets you turn Vision file tracing on and off. Possible values are from "0" to "9"; the higher the number, the more detailed the trace file. A value of "0" or "-1" turns file tracing off. By default, the file is named "vision_trace.log".
AcuODBC Driver Tracing
The trace file lists all the SQL command operations attempted by AcuODBC. This activity is essentially internal to the ODBC driver.
This field lets you turn AcuODBC tracing on and off. Possible values are from "0" to "2"; the higher the number, the more detailed the trace file. A value of "0" turns AcuODBC tracing off.
| 0 | no trace |
| 1 | ISAM trace |
| 2 | SQL trace plus a message box with some errors (e.g., "File not found!") |
SQL Tracing
This trace file lists calls that the ODBC Administrator is passing between the ODBC driver and the application driver. Possible values are from "0" to "2"; the higher the number, the more detailed the trace file. This field lets you turn SQL tracing on and off. A value of "0" means SQL tracing is turned off.
By default, the trace file is named "sql_trace.log".
General notes about traces
You can run each trace operation individually or use the "Start All" and "End All" buttons at the bottom of the tab if you activate more than one trace. The Start buttons affect what happens the next time you use this data source. Changing the settings does not affect currently active data sources.
You can override the default filenames by entering new filenames or using the Browse buttons.