The Best Multi-User solution?

[Adam]

Hi,

The db system is situated in a node that is on a peer-to-
peer network via a hub.

The db is often updated by three employees.

When it is being updated problems develop when one user
cannot do an update because another user is using the
system, and conflicts often develop.

So, I am thinking about changing it. From my literature,
replication, splitting, sharing, internet all seem to be
offering better ways to run this db so that more than one
user can update the system.

May I ask if there is an expert out there who knows
the "best" way to develop a multi-user Access db? And how
may users can I have (I thought I read somewhere that if
the system needs more than 15 users would require moving
to SQL Server/ My SQL etc)

Many thanks

Adam

 

[Joseph Meehan]

Hi,

The db system is situated in a node that is on a peer-to-
peer network via a hub.

The db is often updated by three employees.

When it is being updated problems develop when one user
cannot do an update because another user is using the
system, and conflicts often develop.

So, I am thinking about changing it. From my literature,
replication, splitting, sharing, internet all seem to be
offering better ways to run this db so that more than one
user can update the system.

May I ask if there is an expert out there who knows
the "best" way to develop a multi-user Access db? And how
may users can I have (I thought I read somewhere that if
the system needs more than 15 users would require moving
to SQL Server/ My SQL etc)

Many thanks

Adam

About all you can get is some general information. To really answer
your questions will require someone who really knows Access to come and take
a serious look at your systems and then decide what solution may be best for
your.

I can say I have used Access with databases of over 200,000 records and
over 50 users with good success without going to an SQL server. However I
would have to say someone else with those same facts, but maybe a more
limited network, or heavier use by each user may need a different solution.

I can suggest this. A split Access system can do a good job. I chose
to add user level security, which worked well for me. I suggest that if you
have three people doing a lot of data entry you will likely want to batch
those users so they are not trying to update all at one time. The number of
those who are doing mostly viewing and a little editing is less of a
problem. Access like any database has problems with two people editing the
same records at the same time. It does not know if the second one knows
what the first one did. it can cause errors if it does not offer some sort
of lock. In Access the problem can be more confusing because it locks not
individual records, but locks pages. It is not generally clear to the users
how many records may be on the same page.

In short. I believe Access may be a very good tool for you.