Handling concurrency with table adapter manager




I am updating my data on a winform db app as so;


How can I handle data concurrency error in this situation specially when
table adapter manger may be handling more than one data adapter/data table?



William Vaughn \(MVP\)

Again, I discuss several concurrency strategies in my book but I generally
try to design the application and structure the data to prevent
collisions--not try to figure out what to do after they occur. When an
Update fails due to a collision (and it's not the cause of your own
application), something (or someone) has to decide how to untangle the mess.
Do you force through the last change? (Washington DC approach) Do you simply
accept that a change has beat you to the row? (the "laid-back" approach) or
let the user (eventually) decide.

William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question