FIX: Setting Rst.ActiveConnection to a Recordset Causes GPF (193093)
The information in this article applies to:
- Microsoft Data Access Components 1.5
- Microsoft Data Access Components 2.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q193093 SYMPTOMS
Setting a Recordset's ActiveConnection property to a recordset object
causes either a Dr. Watson or a general protection fault (GPF) error to
occur. For example:
Set rst.ActiveConnection = rst
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
This problem has been fixed in MDAC version 2.1 Service Pack 2.
Under MDAC versions 2.1 Service Pack 2 and later, you will receive the following trappable error as expected:
Run-time error '3001': Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another.
REFERENCES
For more information on how to correctly open recordsets using ADO, please
see the following article in the Microsoft Knowledge Base:
168336 HOWTO: Open ADO Connection and Recordset Objects
Modification Type: | Minor | Last Reviewed: | 3/21/2005 |
---|
Keywords: | kbADO210sp2fix kbbug kbDatabase kbfix kbMDACNoSweep KB193093 |
---|
|