FIX: Oracle Driver Doesn't Sort SQLPrimaryKeys Result Set by Key Sequence (304394)
The information in this article applies to:
- Microsoft ODBC for Oracle version 2.5 Build 2.573.2927
- Microsoft ODBC for Oracle version 2.5 Build 2.573.3513
- Microsoft ODBC for Oracle version 2.5 Build 2.573.3711
- Microsoft ODBC for Oracle version 2.5 Build 2.573.4202
- Microsoft ODBC for Oracle version 2.5 Build 2.573.4403
- Microsoft ODBC for Oracle version 2.5 Build 2.573.5303
- Microsoft ODBC for Oracle version 2.5 Build 2.573.6019
- Microsoft ODBC for Oracle version 2.5 Build 2.573.6526
- Microsoft ODBC for Oracle version 2.5 Build 2.573.7326
- Microsoft ODBC for Oracle version 2.5 Build 2.573.7626
- Microsoft ODBC for Oracle version 2.5 Build 2.573.7713.2
- Microsoft Data Access Components 2.5
- Microsoft Data Access Components 2.6
- Microsoft Data Access Components 2.7
This article was previously published under Q304394 SYMPTOMS
If you call the SQLPrimaryKeys command, and the SchemaName is set to a valid schema name, the Microsoft Oracle Driver does not order the result set that is returned from ODBC Test as expected.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
300635 INFO: How to Obtain the Latest MDAC 2.6 Service Pack
To work around this problem, use Oracle's ODBC Driver.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Data Access Components 2.6 Service Pack 2.REFERENCESFor additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
271852 BUG: MS Oracle ODBC Driver Truncates Spaces in Column Name
Modification Type: | Major | Last Reviewed: | 12/3/2003 |
---|
Keywords: | kbbug kbfix kbmdac260sp2fix kbOracle KB304394 |
---|
|