One way to work around optimistic concurrency issues in ADO is to lock the records your DataSet retrieves as soon as the edit operation begins. This strategy is known as pessimistic locking. Long-duration locks generally lead to poor database performance and contention problems, but in situations where an application cannot tolerate having records changed while it is updating them, pessimistic locking may be necessary.

With ADO, it's relatively easy to use a pessimistic locking scheme. In ADO.NET, it's somewhat more difficult to set up, but you can still use pessimistic locking in your applications. However, just because you can do something doesn’t mean you should do it all the time—what I’m about to explain should be used only when absolutely necessary.

Other Headlines from Builder.com ...
 - Pessimistic locking solves ADO.NET concurrency problems
 - Architecting a CMS in ASP.NET: One server or a bunch of servers?
 - Accessing database data with ASP.NET
 - Plan now to take advantage of .NET application server functionality
 - Achieve pure .NET development with VB.NET

Click here for more Builder.com headlines

More Articles Headlines ...
 - Using the XSD Inference Utility
 - TaskVision Solution Overview: Design and Implementation
 - Creating Assemblies On The Fly Using Code DOM
 - Obtaining System Information
 - CodeDOM: How to achieve code generation in .NET - Part 1