BUG: Function dbcursorfetch Fails with Error 221

Last reviewed: April 29, 1997
Article ID: Q108685

The information in this article applies to:

Microsoft SQL Server Programmer's Toolkit, version 4.2

BUG# 9696 (4.20.50)

SYMPTOMS

When calling DB-Library function dbcursorfetch with the FETCH_NEXT option in a medium-model MS-DOS application, the function call fails, generating error 221:

   Column of type (%s) does not allow nulls. It may not be compared
   with null.

CAUSE

When building the query to perform the cursor fetch, DB-Library is incorrectly attempting to compare a NOT NULL column with the value NULL.

WORKAROUND

For MS-DOS programs, use the large-model DB-Library. The function dbcursorfetch behaves correctly on other operating systems.

STATUS

Microsoft has confirmed this to be a problem in DB-Library version 4.20.50. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: db-lib dblib cursors
Keywords : kbprg SSrvDB_Lib SSrvProg
Version : 4.2.5
Platform : MS-DOS

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.