BUG: Error Disassociating Resultset from rdoConnection (173991)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q173991 SYMPTOMS
Attempting to disassociate a Resultset based on a parameterized rdoQuery
object by setting the Resultset's ActiveConnection property to Nothing will
result in an error:
Run-Time Error '40070':
This property or method is not supported when using the currently
selected cursor library.
CAUSE
This problem occurs when the Resultset is based on a parameterized rdoQuery
object. It also occurs using the UserConnection object with the same
circumstances.
RESOLUTION
The only workaround is to not use a parameterized rdoQuery object to create
a Resultset.
You can set the Resultset ActiveConnection property to Nothing if: - The Resultset is based on a SQL Select statement or a non-parameter
rdoQuery,
-and- - the CursorDriver is rdUseClientBatch, the type is rdOpenStatic, and the
l ocktype is rdConcurBatch.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.
Modification Type: | Major | Last Reviewed: | 11/5/2003 |
---|
Keywords: | kbBug kbpending kbRDO KB173991 |
---|
|