Multi user application

[Corobori]

After years of developing single user application I have been asked to
write a multi user application.

Here is my question: what should I really take care of developing such
application ? How do I deal with update ? Do I have to timestamp all
records and checked that manually ?

My backend will a SQL Server database and my frontend will be a windows
form application written in VB.NET

[Kerry Moorman]

RE: Multi user application

Corobori,

You have to deal with concurrency issues one way or another.

I think that using SQL Server timestamps is a great way to go because it is
so straightforward to code and SQL Server updates the timestamps
automatically when a record in the table changes.

Of course, you still have to manually use the timestamp to deal with
concurrency.

Kerry Moorman


"Corobori" wrote:
[color=blue]
> After years of developing single user application I have been asked to
> write a multi user application.
>
> Here is my question: what should I really take care of developing such
> application ? How do I deal with update ? Do I have to timestamp all
> records and checked that manually ?
>
> My backend will a SQL Server database and my frontend will be a windows
> form application written in VB.NET
>
>[/color]

[Cor Ligthert]

Re: Multi user application

Corobori,

When you want to go with dotNet you hopefully have not to deal with
timestamps.

AdoNet is based on optimistic concurrency. The idea by that is, that you can
better let the user make some corrections than to let him endless wait
because another user has locked a record and started meanwhile drinking his
coffee.

This does not mean that this is forever the best, however AdoNet is
primaraly based on that.

There are enough articles on msdn about concurrency and how to handle
concurrency errors.

Here an article about concurrency in general
http://msdn.microsoft.com/library/de...oncurrency.asp

I hope this gives some idea's

Cor