FIX: Update on View-based Cursor Fails to Modify Row if View Contains a Join

Article translations Article translations
Article ID: 238547 - View products that this article applies to.
This article was previously published under Q238547
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56059 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

An update, with a cursor that is based on a view, can fail to update a row if the view is based on a join of one or more tables. ODBC applications may encounter a SQL_SUCCESS_WITH_INFO message "Cursor operation conflict" in this situation because no rows were affected by the cursor update. If you are using an ANSI T-SQL based cursor, an UPDATE statement in this scenario fails with the following error:
Msg 16947, Level 16, State 1
No rows were updated or deleted.

WORKAROUND

Define the cursor with the query on which the view is defined.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 238547 - Last Review: October 21, 2013 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB238547

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com