Bug #11756 | Feature Request: include myodbc3d.dll in Windows Binary distribution | ||
---|---|---|---|
Submitted: | 6 Jul 2005 3:36 | Modified: | 19 Jul 2007 0:42 |
Reporter: | Steve Revilak | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | Connector / ODBC | Severity: | S4 (Feature request) |
Version: | 3.51.11-2 | OS: | Windows (Windows XP SP2) |
Assigned to: | Kent Boortz | CPU Architecture: | Any |
[6 Jul 2005 3:36]
Steve Revilak
[1 Aug 2006 15:05]
Dave Neary
Hi, I have the same problem (I need to trace ODBC calls from a client, but I don't have the myodbc3d.dll file). In addition, when I copied the myodbc3d.dll file from 3.51.04 it didn't work with my (4.1.x) server, because it didn't support the new password handling. I'd prefer to have an updated debug DLL than handicap the server to use old-style passwords, or even replace the password for the DB user by an old-style password. Dave.
[19 Jul 2007 0:42]
Kent Boortz
There might be a "myodbc3d.dll" in 3.51.18 (not decided yet), but it would have the same features as the normal one, just debug compiled for more easy debugging in Visual Studio and similar. In 3.51.18 the driver level tracing will be removed. We recommend the use of driver manager tracing. On Windows, this can be enabled in "ODBC Data Source Administrator" that you can find from the Control panel and "Administrative Tools".