Okay, how about this approach: it's probably safe to assume that whether or not to do ODBC tracing is on is in the registry somewhere. So I'd say make a dump of the registry, change the setting in the control panel, make another dump and compare the two dumps. That'll show you what to change in the registry. Alternatively, you could download regmon from www.sysinternals.com and run it while changing the setting. That'll show you what key has to be changed.
cheers,
roel
Truckle, Andrew J wrote:
It's probably worth pointing out one of the statements in the docs that -may- catch you out....
Under "TraceSQLMode" entry: ...This entry is interchangeable with SQLTraceMode....
Might be worth checking for the first (TraceSQLMode) and, if it doesn't exist, check for the other (SQLTraceMode).
Could, possibly, be for backwards compatibility. *shrug*
I did notice that too. But unfortunately, changing this registry setting to 0 makes no differenence whatsoever. If you go to the Control Panel / ODBC Data Sources / Tracing property page the tracing mechanism is still on. Infact, starting / stopping it from that property page seems to have no affect on the registry key.
Andrew
This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.
_______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
_______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
