• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 294
  • Last Modified:

Simultaneous users - how many users can have a DB open at the same time

Hello there,

I have developed a simple Access database (recruitment) and we have entered all the necessary data. Now all entries have to be reviewed by the relevant departments and everyone may have to do certain modifications to the entries (the data, not the design of the DB objects), approximately 30 people at the same time.
Today I was told that some people - when opening the database - would receive a message that it was read-only. The DB is shared on a folder running Windows Server 2003, the permissions are correct (I asked them to try and copy a Word document into that folder, try to modify it and save it and it was possible), so it can't be that. I tried opening the DB myself (I'm the Admin) and I get the same error message.
As a result, I assume that this is an Access restriction (maybe total number of simultaneous users opening the DB). Or maybe something else? Maybe I have to create a Workgroup file? I'm not really an Access expert, so any step by step guide would be really ehlpful.
Thanks in advance.
0
ntossiou
Asked:
ntossiou
  • 4
  • 4
  • 2
  • +2
4 Solutions
 
jerryb30Commented:
Are users opening the db directly, instead of using a local front end?
We had a similar set-up a few years back, and there was a limit of about 10 simultaneous users, but that was an OS thing.
0
 
jerryb30Commented:
Your solution, if you do not have local front ends, is to go to that model.
Create a db with everything in the back-end db except the tables, and then link to the tables in the back-end db.
0
 
ntossiouAuthor Commented:
Yes, the DB resides on a shared folder on a server, which is mapped as drive Z on the client computers through group policy, there is no local front-end.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
The max # of users is (theoretically) 255.

This error many times can occur if one or more users do not have FULL Access to the folder holding the MDB.

mx
0
 
ntossiouAuthor Commented:
So the procedure would be to move the tables to a new MDB file, put that on the server, give a copy of the other MDB file to all users and link the user MDB file to the tables on the server MDB file?
0
 
jerryb30Commented:
See previous comment.
Access can handle more than 30 users (per specs), although it is hardly the best db for that.  But you really do want to use a front-end/back-end schema.
0
 
jerryb30Commented:
>>So the procedure would be to move the tables to a new MDB file, put that on the server, give a copy of the other MDB file to all users and link the user MDB file to the tables on the server MDB file?
Ed Zachary. Yes.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<So the procedure would be to move the tables to a new MDB file, put that on the server, give a copy of the other MDB file to all users and link the user MDB file to the tables on the server MDB file?>>

  Yes, exactly.

JimD
0
 
ntossiouAuthor Commented:
Thanks for all your comments.
I will try it (hopefully tomorrow, if not Monday) and I'll get back to you!
0
 
Rick_RickardsCommented:
MX is right about 255 users so 30 shouldn't be an issue.  Some things that might help are....

Split the database so all users access the backend thru a front end.  My thought is that someone may be gaining exclusive access to your .mdb by opening up something in design view w/o realizing the chaos that they have then brought to bear (even after they have closed the object).  If everyone's running a front end then that will put an end to this problem.

To create front ends for your users to try instead of having everyone access the server's copy just copy the server's .mdb, delete all the tables than from your workstation tell access you'd like to create a new table (a linked table), point it to where the server copy resides and then select every table there as a linked copy.  Exceptions would be any table used as a temporary or hash table, (something that one could have locally and preferably so it doesn't interfere with or even involve another user.
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Basically you want a split mdb scenario (industry standard). Front End (forms, reports, queries, vba code) and a Back End mdb (tables only).  You can use the Database Splitter to do this easily.  Then, each FE is linked to the same back end.  This alone many times will eliminate the problem you are having.

mx
0
 
ntossiouAuthor Commented:
Thanks for all answers, jerryb30 gets 200 points because he was the fastest (I hope it's fair).
Thanks again everybody.
0
 
Rick_RickardsCommented:
Just glad you got the answer you were looking for.

Rick
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 4
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now