A
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
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