Though this isn't a .Net issue, I thought I'd post here anyway ...
I'm ODBC trace-ing an old VB6 app in order to pick out and modify the relevant stored procs. First time I turned trace on, everything was golden, got a log file. Ever since that time, no log file, with many, many, MANY repeated efforts, and even reboots -- not with the default trace utility in the Data Sources admin in XP Pro, nor with the add-on MS ODBC trace program. And the path hasn't changed.
Eventually I resorted to directly editing the registry to enable tracing:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC
Value name: Trace
Original value was 0; I enable tracing by setting value to 1, disable tracing by setting value back to 0. Seems to work like a charm.
.NET Development2
|