Article ID: 45262
Article Last Modified on 3/2/2005
APPLIES TO
- Microsoft SQL Server 4.21a Standard Edition
This article was previously published under Q45262
If an update issued by user 1 during a browse fails because user 2 has updated the record since user 1 read it, you can optionally override the timestamp protection and force the update to occur by issuing the update without the timestamp qualification in the WHERE clause. If user 2 has changed the columns(s) that uniquely identify the row, the update results in a "not_found" error. Then do an insert.
Additional query words: Transact-SQL
Keywords: kbother KB45262
