BUG: dbbind Converts char Column w/ Leading Spaces to Zero

Last reviewed: April 29, 1997
Article ID: Q114262

The information in this article applies to:

Microsoft SQL Server Programmer's Toolkit, version 4.2

BUG# 9985 (4.2)

SYMPTOMS

When using dbbind function to convert a char or varchar column with leading spaces to an integer, the integer is always set to 0. However, if the Transact SQL CONVERT statement or the dbconvert function is used, the string is converted correctly; the leading spaces are ignored.

NOTE: The problem happens in DB-Library (DB-Lib) versions 4.20.50 and 4.21.00.

WORKAROUND

A workaround is to use the Transact SQL CONVERT statement to convert the character string in the result set to integer before binding to a program variable, or use dbconvert instead of dbbind.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2 and Microsoft SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: dblib Windows NT
Keywords : kbbug4.20 kbprg SSrvDB_Lib SSrvProg
Version : 4.2 | 4.2
Platform : OS/2 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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.