PRB: ADO Run-Time Error with Update/Delete and SET NOCOUNT ON (195491)
The information in this article applies to:
- ActiveX Data Objects (ADO) 1.5
- ActiveX Data Objects (ADO) 2.0
- ActiveX Data Objects (ADO) 2.1 SP2
- ActiveX Data Objects (ADO) 2.5
- ActiveX Data Objects (ADO) 2.6
- ActiveX Data Objects (ADO) 2.7
This article was previously published under Q195491 SYMPTOMS The following run-time errors may occur when you try to
Update/Delete data with an ActiveX Data Objects (ADO) server-side cursor:
Cursor operation conflict. -or-
Errors occurred. Using ADO 2.1 Service Pack 2
(SP2) and earlier versions, the MSDASQL provider generates the former error
message and the SQLOLEDB provider generates the latter. Using ADO 2.5, both
providers generate the "Cursor operation conflict" error. NOTE:
Although the error message occurs, the Update/Delete succeeds. CAUSE SQL Server is using the following configuration options:
sp_configure "user options", 512
RESOLUTION Change the cursor location to adUseClient or trap the
run-time error in Visual Basic. Because the Update/Delete actually succeeds,
you can ignore the error message. STATUS This behavior is by design. REFERENCES
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
195225
PRB: DAO Run-Time Error 3146 When Modifying SQLServer Data
Transact - SQL Reference Help, search on: "sp_configure"
Transact - SQL Reference Help, search on: "SET"
Modification Type: | Minor | Last Reviewed: | 3/2/2005 |
---|
Keywords: | kbDatabase kbprb KB195491 |
---|
|