An Access database with simultaneous multiple users

Having a Access database that is accessed by simultaneous multiple users.  Can that be a problem?
Lawrence AverySystem DeveloperAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Daniel KlineSr. SharePoint DeveloperCommented:
If all the users are accessing the same database file, it should not be a problem.  However, if you have enough users to overwhelm the power of the machine serving up the database file, you may have issues first in performance and then with a failure when sessions timeout and data is lost because the server does not respond in a reasonable amount of time.
0
Dale FyeCommented:
Generally, as long as each user has their own front-end (application) ON THEIR PC (not shared) and the tables in that application linked to a common backend database containing only the data files, located on a network file share, you should not have a problem.

However, this will be influenced by the speed of the network and the number of simultaneous users.  I've generally had good success with up to 25 simultaneous users, but that will depend on your network bandwidth.
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
To add a couple comments:

1. To Dale's point, the stability of the network and the stations is the largest problem.

2. It's important to understand that with a JET/ACE data store, the sever acts as nothing more than a file share.  All the DB processing is carried out client side.  There is no server side process running.

Given the above, you generally can run up to about 30-40 without issue if good application design and development.   Beyond that, it's hard to keep a stable environment.   At that point anyway, your starting to look for other features, such as on-line backups, and roll back and roll forward operations.   This is where most switch to SQL Server for the data store and keep the Access Front End.

 To further this point, I've seen a 200+ user reporting app that was mostly read-only.  So primarily  the issue is not one of performance (unless your running in the millions of records), but with stability.

Jim.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
:-)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.