Multiple users on a split database

D

Dan

I will be setting up a split database to log help line calls. I expect to
average three calls per week to each of eight people answering the calls.
Since this will amount to an average of twenty-four calls a week, what
happens when more than one person using the database tries to save data to
the back-end database at the same time? Can there be conflicts and how would
one avoid them? Is the probability of conflict so low that I can disregard?
Thanks for any input!
 
M

Mark

The only real conflict would be if two people were trying to edit the same
record at the same time, which would be rare; especially if they are always
creating new records as they log their incoming calls.
 
J

John Vinson

I will be setting up a split database to log help line calls. I expect to
average three calls per week to each of eight people answering the calls.
Since this will amount to an average of twenty-four calls a week, what
happens when more than one person using the database tries to save data to
the back-end database at the same time? Can there be conflicts and how would
one avoid them? Is the probability of conflict so low that I can disregard?
Thanks for any input!

I'm working with a client with a dispatching system (animal shelter)
averaging about 100 calls a DAY from between three and ten operators
updating concurrently. Sure, there are occasional problems - but data
conflicts aren't among them.

If each user is creating new records in the table for each call, the
Access JET engine is quite capable of handling the conflicts that may
arise.

If you're assuming that only one person can use the entire database at
a time, you're overly pessimistic: Access is formally limited to 255
concurrent users. In practice, forty or fifty concurrent *updating*
users, and well over a hundred concurrent reading users, can be
handled without major difficulty.

John W. Vinson[MVP]
 
D

Dan

Thanks, Mark. I don't anticipate this happening.

Mark said:
The only real conflict would be if two people were trying to edit the same
record at the same time, which would be rare; especially if they are always
creating new records as they log their incoming calls.
 
Top