BUG: SQLSetPos(SQL_ADD) Error 2750 on Keyset Cursor

Last reviewed: May 5, 1997
Article ID: Q153300

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG#: 15517 (6.0) (sqlserver)

SYMPTOMS

If a client computer running the Japanese version of Windows NT attempts a SQLSetPos(SQL_ADD) on a keyset cursor, the Microsoft SQL Server ODBC Driver may incorrectly generate the following error:

   SQLState = 37000, pfNative =  2750
   szErrorMsg = '[Microsoft][ODBC SQL Server Driver][SQL Server]
                 Column or parameter #5: -- specified column
     precision 49 is greater than the maximum precision
     of 38.'

STATUS

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

WORKAROUND

Insert the row using an insert command, or use forward only cursors.

MORE INFORMATION

Some 2750 errors returned on a SQLSetPos will be valid if the application has specified a precision on SQLBindCol that is larger than that supported by the associated column in SQL Server. However, in some cases on Japanese clients this error may be raised incorrectly. The problem is specific to the 2.50.0126 driver that ships with SQL Server Service Packs 1 and 2. It does not occur on the 2.50.0121 driver that ships with SQL Server 6.0, or with the 2.65.0201 driver that ships with SQL Server 6.5.


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