Article ID: 197449 - View products that this article applies to.
This article was previously published under Q197449
When you use a single command object to open multiple recordset objects with one or more of those recordset objects open at the same time, you encounter unexpected behavior. This is most noticeable when you open stored procedures with output or return parameters.
Consider the following ActiveX Data Objects (ADO) code, which is written in Visual Basic for Applications:
Note You must change UID=<username> and PWD=<strong password> to the correct values before you run this code. Make sure that UID has the appropriate permissions to perform this operation on the database.ion on the database.
At this point, the Parameters collection for the command object has two objects, and you can reference them as you would normally. However, consider the following code, which destroys (resets) the Parameters collection:
At this point, the Parameters collection has been reset to contain only one Parameter object. However, the original Recordset (rs1), which has not been closed or released, still has a reference to an internal buffer that stores the value of each parameter that was originally created. When the original recordset is closed, it attempts to release the buffer. However, the second recordset's Parameters collection may be using the same memory location for its own buffers, and if both recordsets are trying to release the same memory location, you may receive an Access Violation.
The Access Violation has been confirmed to occur (at random intervals) when using a forward only cursor with a parameterized stored procedure using the OLE DB Provider for ODBC to the SQL Server ODBC Driver. It may occur with other ODBC Drivers or OLE DB Providers as well.
The Access Violation appears to have been fixed in the MDAC 2.1 SP2 release. However, recycling the same Command Object for multiple, concurrently open Recordsets is not a safe practice. Any savings in performance or memory allocation you receive in minimizing the number of created objects will not be compensated for by increased risk of your code causing a failure within ADO. The Command Object is not designed or intended for this kind of utilization.
Article ID: 197449 - Last Review: March 14, 2005 - Revision: 2.1
Contact us for more help
Connect with Answer Desk for expert help.