do I have to take care of concurrency?

[imad]

Hi,
I have devloped a vb application and I want to install it on a network of 10 computers.I just have one approach in mind and I don't know if it's the best approach.I want to install my application on each pc and I'll install the sql server database only on one pc an I'll make sure that the connection string in all installed applications points to the pc/server where the sql server resides.
Is this the best approach? Also do I have to take care of concurrency issues or it's handled by the database itself?Please give me some hints or example on how to handle the concurrency problems in code.
thank you in advance

 

[jmcilhinney]

It certainly is the best approach to install the database on only one machine if you intend every user to access the same database.

As for concurrency, there are various ways to handle it. Let's say that user A retrieves some data. User B then retrieves the same data, edits it and saves it. User A then edits the data and tries to save it. What do you want to happen? You can configure ADO.NET to use last-in-wins, pessimistic or optimistic concurrency. You can read about each and how to implement them on MSDN.

 

[ScottyB]

Hi

Here is an interesting article on the different types of concurrency management strategies and how to deal with them.

http://www.devx.com/codemag/Article/32160

Hope this helps

Kind Regards

ScottyB