Hi, In case of high volume transaction applications one major aspect which needs to be considered while developement is to tackle/avoid the concurrency errors.
There can be several standard techniques/approaches used to check this like - 1. Timestamp method for checking the data change 2. Data adapter handles the locking internally. etc.. I would like to know are there any other approaches/solutions in .Net that can be used to avoid the concurrency errors or multiple user accesssing same record scenario? Are there any other ways apart from the 2 i mentioned above? Kindly share your experiences/thoughts in how this scenario is tackled in such high volume transactional applications. Regards Hrishi Kindly give your thoughts on this topic. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
