more users

[antonov]

hello everybody.... just a quick question: is it possible to make sure that
2 or more people can update THE SAME record? if so... how?
thanks

 

[dbahooker]

use Access Data Projects.

MDB is obsolete and anyone that still uses it should be FIRED and then
SPIT UPON.


-Aaron

 

[John Vinson]

hello everybody.... just a quick question: is it possible to make sure that
2 or more people can update THE SAME record? if so... how?
thanks

Two or more people can update the same record IF they do it at
different times.

Only one person can update the same record at the same time. Think
about it: if Joe updates AmountDue to 100 at the same moment that
Janet updates AmountDue to 150, what is the correct value of
AmountDue? YOU HAVE A CONFLICT and there is no unambiguous answer. The
solution Access takes is either "optimistic locking" - in which case
the value entered by the first user gets stored, and the second user
gets a warning that the value has been changed; or "pessimistic
locking", in which case the second user simply isn't permitted to edit
the record until the first user is done.

What business problem are you trying to solve, and what provisions do
you have in mind for resolving the conflicts that will arise?

John W. Vinson[MVP]

 

[dbahooker]

John

with MDB you have close to NO CONTROL over locking.

with ADP you can always use query locking hints in order to cut down on
problems.

Stop defending a DEAD PROGRAM, John.
Lose the training wheels you WIMP.

-Aaron

 

[antonov]

I am not trying to solve any problem, right now. I am just looking ahead...
I am making this program which will be used by 3 different departments. I
just need to know if there is a possibility to update the data... but how
big is the chance that 2 people will update the same record at exactely the
same time?

 

[John Vinson]

I am not trying to solve any problem, right now. I am just looking ahead...
I am making this program which will be used by 3 different departments. I
just need to know if there is a possibility to update the data... but how
big is the chance that 2 people will update the same record at exactely the
same time?

That depends entirely on your data. Do different departments routinely
need to update the information in one and the same record? I don't
know, since I don't know what's in your database or what your
departments do with it!

The very WORST that will happen is that one user will get a warning
message and have to reenter one record - or, more likely, wait a few
seconds and try again.

John W. Vinson[MVP]

 

[Larry Linson]

That depends entirely on your data. Do different
departments routinely need to update the information
in one and the same record? I don't know, since I
don't know what's in your database or what your
departments do with it!

The very WORST that will happen is that one user
will get a warning message and have to reenter one
record - or, more likely, wait a few seconds and
try again.

My observation (developing Access DBs for business applications since 1993)
is that most business processes are such that it is just not a common
occurrence for multiple users to actually be updating the same record at the
same time. But, as you say, it is data and process dependent!

I'd say to the original poster -- don't waste a lot of time and energy
worrying about this particular aspect of your application; if it turns out
that yours is one of the uncommon cases where it does happen with some
frequency, it will not be a difficult situation for you to handle; and
chances are good, you just will not have a problem.

Larry Linson
Microsoft Access MVP

 

[dbahooker]

or of course; you can use a REAL DATABASE like SQL Server and Access
Data Projects.. and then you can prevent locking problems by using the
WITH (NOLOCK) clause.

using MDB; and sitting there and hoping for the best isn't a good
strategy

-Aaron