BUG: SQLGetInfo Gives Incorrect Result for SQL_DRIVER_HSTMT

Last reviewed: December 20, 1996
Article ID: Q161354

The information in this article applies to:

Microsoft Open Database Connectivity, version 3.0

BUG #: 4469 (odbc30)

SYMPTOMS

SQLGetInfo may return the incorrect result for the SQL_DRIVER_HSTMT option if both of the following conditions are true:

The ODBC application is a 16-bit application.
-and-
The ODBC driver is 32-bit, and was compiled under the ODBC 2.5 SDK.

The 16-bit ODBC application will encounter this problem only when using the ODBC SDK 3.0 thunking layer.

WORKAROUND

To work around this problem, use the thunking layer that came with the ODBC 2.5 SDK. The following files need to be replaced:

   Ds16gt.dll
   Ds32gt.dll
   Odbc16gt.dll
   Odbc32gt.dll

STATUS

Microsoft has confirmed this to be a problem in Open Database Connectivity version 3.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbprg kbbug3.00 kbother
KBSubcategory: SSrvProg
Additional reference words: vc sql server

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 20, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.