Microsoft KB Archive/286213

= PRB: Second Parameterized Command Fails with Server Cursor =

Article ID: 286213

Article Last Modified on 11/3/2003

-

APPLIES TO


 * Microsoft Data Access Components 1.5
 * Microsoft Data Access Components 2.0
 * Microsoft Data Access Components 2.1
 * Microsoft Data Access Components 2.5
 * Microsoft Data Access Components 2.6
 * Microsoft OLE DB Provider for SQL Server 7.0
 * Microsoft OLE DB Provider for SQL Server 7.01
 * Microsoft OLE DB Provider for SQL Server 2000 2000.80.194

-



This article was previously published under Q286213



SYMPTOMS
If you open a session using the SQLOLEDB OLEDB provider specifying DBPROP_MULTIPLECONNECTIONS = VARIANT_FALSE, and then attempt to run multiple parameterized selects (using server cursors, which allow multiple active statements per session), the second and subsequent commands may fail with an &quot;Object is open&quot; error.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
When opening a session using the SQLOLEDB OLEDB provider, you can set the DBPROP_MULTIPLECONNECTIONS property to VARIANT_FALSE to disable the provider from making additional connections internally. Therefore, with DBPROP_MULTIPLECONNECTIONS set to VARIANT_FALSE, SQLOLEDB will only use one connection to the SQL Server for the session. By default, this property is set to VARIANT_TRUE, which allows SQLOLEDB to open multiple connections per session if needed.

Internally, the SQLOLEDB OLEDB provider may need to open an additional connection to obtain metadata for existing pending SQL statements. For example, if you prepare a parameterized SQL statement, SQLOLEDB may need to request metadata for the parameters if you do not explicitly set the parameter information. It is this situation that causes the &quot;Object is open&quot; error.

Additional query words: MULTIPLECONNECTIONS multiple statements

Keywords: kbprb KB286213

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.