PRB: ActiveX Data Objects Update Method Fails When the SELECT Statement Contains a Subquery (262934)
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 Q262934 SYMPTOMS
When you call the Update method of an ActiveX Data Objects (ADO) recordset that is opened on a SQL statement that also contains a sub-select using the Microsoft ODBC Driver for Oracle, then the following error message occurs:
[Microsoft][ODBC driver for Oracle]"Cannot use Keyset-driven cursor on join, with distinct clause, union, intersect or minus or on read only result set"
State:S1C00,Native:0
This error message does not occur if a SQL statement does not contain a sub-select.
RESOLUTION
Following are two possible work-arounds for this behavior:
- Avoid sub-queries when you build an updateable rowset.
- Set the cursor location to use client-side cursors.
Modification Type: | Major | Last Reviewed: | 12/5/2003 |
---|
Keywords: | kbDatabase kbnofix kbOracle kbprb KB262934 |
---|
|