DynDeveloper.com

DynDeveloper.com

Sign Up Now!Log In
Kaprice 8/1/2019 8:03:55 PM

RadGrid - Concurrency best practices

I'm implementing a RadGrid control, bound to SQL Server table, and which will be used by up to 12 people at a time. What's the best way to handle concurrency (to be clear, I mean when one person makes a change while others are working or viewing the same records and fields)?

My client likes the idea of having changes submit to the database on a per cell basis. If a User changes a cell, it gets saved to the DB as soon as the User leaves edit mode of that cell.

If we go that route, what's a good way to deal with the others who may be VIEWING data that's no longer current?

Version: Unknown or N/A
Section: .NET Development, Telerik