Question about Dataset

  • Thread starter Thread starter Michael Wong
  • Start date Start date
M

Michael Wong

Hi,

I am new to ADO.NET and ADO in general.
I have successfully created my first application to access an Access
database using a Dataset and Grid control.

If I understand, a Dataset is a snapshot of the data contained in the
database. From the Dataset, the user modify it and then update it back to
the database.

A question I have is how does it manage under a multiuser environment.

Let me explain myself. The database.mdb is on a network which users access
with there application (using Dataset).
What if two users modified the same data row at the same time?
 
We have discussed this many times so I suggest doing a bit of research on
the archives of this list (use Google groups). Search for "concurrency" and
"optimistic".
Generally, I suggest that folks design systems that don't collide. That is,
I build systems where the ownership of data is clearly defined. This way a
user can fetch data as needed and have no concern that other users are
changing the data being worked on. Yes, there are case where this is not
possible so you'll have to come up with some "rules" that say what changes
will be permitted, by whom and when. When you get ADO.NET to post the
updates there are a variety of techniques to tell if the row has changed
since last read. If your code senses a change you have to decide what to do
about it. I discuss this at length in my book.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Thanks William, I'll search them with Google.

William (Bill) Vaughn said:
We have discussed this many times so I suggest doing a bit of research on
the archives of this list (use Google groups). Search for "concurrency" and
"optimistic".
Generally, I suggest that folks design systems that don't collide. That is,
I build systems where the ownership of data is clearly defined. This way a
user can fetch data as needed and have no concern that other users are
changing the data being worked on. Yes, there are case where this is not
possible so you'll have to come up with some "rules" that say what changes
will be permitted, by whom and when. When you get ADO.NET to post the
updates there are a variety of techniques to tell if the row has changed
since last read. If your code senses a change you have to decide what to do
about it. I discuss this at length in my book.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Click to expand...
 
Back
Top