BUG: ODBC OrdinalPosition Differs with dbSQLPassThrough (129731)
The information in this article applies to:
- Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
This article was previously published under Q129731 SYMPTOMS
The values of OrdinalPosition for fields in a RecordSet created against an
ODBC data source will be different depending on whether dbSQLPassThrough is
used or not.
CAUSE
OrdinalPosition is not under the control of Visual Basic DAO for ODBC data
sources. This information is retrieved from the back-end database engine.
RESOLUTION
OrdinalPosition on a database should not be expected to be in sync with
collection indexes in Visual Basic. To get the OrdinalPosition as defined
for the ODBC datasource, dbSQLPassThrough should be used.
STATUS
Regarding: The difference in OrdinalPosition with or without
dbSQLPassThrough:
Microsoft has confirmed this to be a bug in the products listed at the
beginning of this article. We are researching this problem and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
Regarding: The difference in OrdinalPosition versus the value in collection
indexes:
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 12/9/2003 |
---|
Keywords: | kbbug kbDatabase KB129731 |
---|
|