FIX: Dynamic Cursor Fails to Delete a Record (159373)

The information in this article applies to:

Microsoft SQL Server 6.5
Microsoft Open Database Connectivity 2.5

This article was previously published under Q159373

BUG #: 16127 (SQL 6.5)

SYMPTOMS

If a dynamic cursor is opened with optccval for the optimistic concurrency control, and ROWSET_SIZE is equal to 1, it may generate the following error message when you attempt to delete a record:

Msg 16934, Level 16, State 2, Optimistic concurrency check failed, the
row was modified outside of this cursor

An Open Database Connectivity (ODBC) application may receive this error message using SQLSetPos to delete a record with the dynamic server side cursor.

WORKAROUND

To work around this problem, use other types of cursors (for example, use the SCROLL cursor type). Use the DECLARE <cursor name> SCROLL CURSOR FOR <statement> syntax for cursors. This will change the cursor type from DYNAMIC to SCROLLABLE (keyset-driven).

An ODBC application can use either ODBC cursors or keyset-driven server side cursors.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5 and Open Database Connectivity 2.5. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Modification Type:	Major	Last Reviewed:	10/16/2003
Keywords:	kbBug kbfix kbusage KB159373