| Bug #33645 | SQLDriverConnect fails - hwnd=0, completionFlag = SQL_DRIVER_COMPLETE | ||
|---|---|---|---|
| Submitted: | 3 Jan 2008 1:40 | Modified: | 3 Jan 2008 1:45 |
| Reporter: | Cristian Tarsoaga | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 3.51.12, 3.51.22r857 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | SQLDriverConnect SQL_DrIVER_COMPLETE hwnd NULL | ||
[3 Jan 2008 1:42]
Cristian Tarsoaga
suggested patch for 3.51.12
Attachment: myodbc3.51.12_driver_connect.patch (application/octet-stream, text), 566 bytes.
[3 Jan 2008 1:45]
Jim Winstead
This was fixed in 3.51.18.
[3 Jan 2008 1:55]
Cristian Tarsoaga
suggested patch for 3.51.12
Attachment: myodbc3.51.12_driver_connect.patch (application/octet-stream, text), 566 bytes.
Description: if calling SQLDriverConnect( hdbc, 0 /*hwnd*/, ( SQLCHAR * ) szConnect, ( SQLSMALLINT ) strlen( szConnect ), ( SQLCHAR * ) szConnStrOut, cbConnStrOutMax, &cbConnStrOut, SQL_DRIVER_COMPLETE ); an exception is thrown (setup cannot be opened) but this makes no sense since SQL_DRIVER_COMPLETE means the completion is not needed, or? How to repeat: Repeat: see above Suggested fix: I'll attach a sample patch (for 3.51.12)