BUG: ODBC Driver Misses ANSItoOEM with Server Cursors

 Last reviewed: April 15, 1997
Article ID: Q153847
The information in this article applies to:
  • Microsoft SQL Server version 6.0

SYMPTOMS

The Microsoft SQL Server ODBC Driver does not perform ANSItoOEM conversion successfully when using SQL Server server cursors.

WORKAROUND

Use a forward-only cursor with a rowset size of 1, which will have the driver not use server cursors.

MORE INFORMATION

SQL Server 6.0 introduced server cursors, which are used by the 2.5 versions of the Microsoft SQL Server ODBC Drivers to support ODBC static, keyset, and dynamic cursors. When an ODBC application connected to a SQL Server 6.0 running an OEM code page (such as code page 850) does a SQLSetStmtOption to set the SQL_CURSOR_TYPE to one which will use server cursors, the ANSItoOEM conversions will not be done for those result sets.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft SQL Server ODBC Driver version 2.50.0121. The problem does not occur in version 2.65.0201 of the driver.

Additional query words: SQLBindCol SQLSetPos
Keywords : kbbug6.00
Version : 6.0
Platform : WINDOWS

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: April 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.