BUG: SQLColumns Returning NULLABLE May Not Be Accurate

Last reviewed: September 9, 1996
Article ID: Q124656

The information in this article applies to:

Microsoft Open Database Connectivity, version 2.0

BUG# QJET: 1845 (2.00.2317)

SYMPTOMS

The behavior discussed in this article pertains to the Microsoft Access driver only. SQLColumns returns NULLABLE=1 for a column that is actually not nullable (for example, the Required property was set to Yes for this column using Microsoft Access).

Use Microsoft Access to create a table called test that has a column called col1 of type text(10). For this column, set the Required property to Yes. As a result, this column does not allow nulls. However, SQLColumns returns NULLABLE=1 for col1, indicating that the column does allow nulls, which is not correct.

STATUS

Microsoft has confirmed this to be a problem in ODBC Access Driver version 2.00.2317. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: 2.00.2317 ODBC MFC VISUAL C++ MSVC
Desktop Database Drivers Pack Windows NT
KBCategory: kbprg
KBSubcategory:

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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.