This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 88%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
Hi I have a winforms gridview that saves records on row by row basis. So basically, when end user changes data and leaves the respective row, changes are pushed to the DB. This works fine until multiple users work on the same row. Then the concurrency error is shown. At this point I need to display the changes to the user to choose which datarow wants to be taken as last. The one in DB, the one in gridview or the proposed one. Saving the chosen row is the problem. The gridview is marked with error, so update is not accepting the selected values. I must say, at this point I cannot refill the adapter since, large portion of data could be in grid and refiling it would be a performance killer. Can someone point me to a direction, with an example. Is there a way this to be done with the SqlDataAdapter.RowUpdating Event since I have strongly typed dataset in this project. Thanks N.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 7.000000000000001%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
Hi @Fullstop ,
To handle concurrency conflicts and ensure data security, consistency and integrity in the connected mode of operation in ADO.net, you should take advantage of transactions. You can leverage the TransactionScope class present in the System.Transactions namespace for efficient transaction management when working with ADO.net.
And please refer to this document.
Best Regards,
Daniel Zhang
Hello,
Since there are many ways to deal with databases e.g. TableAdapter or DataAdapter the following may or may not be the appropriate solution, even if not should provide proper direction. Also you might consider retry logic as explained here.
Myself, I wouldn't be doing it with a datatable. I would be using ADO.NET, database command objects and inline T-SQL parameterized to persist a given row and doing optimistic locking of a given record on the table. I would force the user to reload the row in the grid with the latest record that was persisted to the database that had been changed. I wouldn't be giving any user a choice. It's either force the user to get the latest version of the record from the database and update it with their data or just abandon the update of the record, and that's their choices.