BUG: Unexpected Cursor Behavior with Set NoCount Statement and SQLOLEDB (235566)
The information in this article applies to:
- Microsoft Data Access Components 2.1
- Microsoft Data Access Components 2.5
- Microsoft Data Access Components 2.6
- Microsoft Data Access Components 2.7
- Microsoft OLE DB Provider for SQL Server 7.0
- Microsoft OLE DB Provider for SQL Server 7.01
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q235566 SYMPTOMS
If you try to open a server-side ADO recordset with the "Set NoCount" statement, you would always get ForwardOnly recordset.
This behavior is specific to the OLEDB Provider for SQL Server "SQLOLEDB."
RESOLUTIONUse the OLEDB Provider for ODBC "MSDASQL."
-or-
Open the ADO recordset on the Client Side (Static cursor).
-or-
Remove the "Set NoCount" statement from your SQL string or stored procedure.STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 5/8/2003 |
---|
Keywords: | kbBug kbDatabase kbnofix kbProvider KB235566 |
---|
|