BUG: AbsolutePosition Property Returns Different Results (191515)
The information in this article applies to:
- Microsoft ODBC for Oracle version 2.5 Build 2.573.2927
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
- Microsoft Data Access Components 2.5
This article was previously published under Q191515 SYMPTOMS
When you use the Remote Data Objects (RDO) version 2.0 in either Visual
Basic 5.0 or Visual Basic 6.0, with an Oracle 7.x or 8.x database, using
the Microsoft ODBC for Oracle driver, the AbsolutePosition property of the
rdoResultset object produces different results depending on the Cursor
location as set by the CursorDriver property of the rdoConnection or
rdoEnvironment object.
Using the rdUseServer cursor library, the AbsolutePosition property reports
the last row in the Resultset. When tested a second time it returns the
correct results based on its setting.
If you use either the rdUseODBC or rdUseClientBatch cursor libraries, the
results returned will always be correct.
NOTE: This code has also been tested against Microsoft SQL Server without
error.
RESOLUTION
The workaround is to use a MoveLast on the Recordset or not to use the
CursorDriver properties of rdUseServer or rdUseIfNeeded when the results of
the AbsolutePosition property must be accurate. The CursorDriver properties
of rdUseOdbc and rdUseClientBatch produce accurate AbsolutePosition
property results.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 12/3/2003 |
---|
Keywords: | kbBug kbcode kbDatabase kbDriver kbOracle kbpending KB191515 |
---|
|