BUG: SQLColumns Returning NULLABLE May Not Be Accurate (124656)
The information in this article applies to:
- Microsoft Open Database Connectivity 2.0
This article was previously published under Q124656
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.
| Modification Type: | Major | Last Reviewed: | 7/27/2001 |
|---|
| Keywords: | kbBug KB124656 |
|---|
|