Solved

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

Posted on 2007-11-30
13
287 Views
Last Modified: 2011-04-14
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
Comment
Question by:ntossiou
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
  • 2
  • +2
13 Comments
 
LVL 26

Expert Comment

by:jerryb30
ID: 20383433
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
 
LVL 26

Expert Comment

by:jerryb30
ID: 20383442
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
 

Author Comment

by:ntossiou
ID: 20383444
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
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 75
ID: 20383455
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
 

Author Comment

by:ntossiou
ID: 20383458
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
 
LVL 26

Expert Comment

by:jerryb30
ID: 20383461
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
 
LVL 26

Accepted Solution

by:
jerryb30 earned 200 total points
ID: 20383467
>>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
 
LVL 57

Assisted Solution

by:Jim Dettman (Microsoft MVP/ EE MVE)
Jim Dettman (Microsoft MVP/ EE MVE) earned 100 total points
ID: 20383470
<<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
 

Author Comment

by:ntossiou
ID: 20383489
Thanks for all your comments.
I will try it (hopefully tomorrow, if not Monday) and I'll get back to you!
0
 
LVL 16

Assisted Solution

by:Rick_Rickards
Rick_Rickards earned 100 total points
ID: 20383508
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
 
LVL 75

Assisted Solution

by:DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform) earned 100 total points
ID: 20383517
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
 

Author Comment

by:ntossiou
ID: 20394489
Thanks for all answers, jerryb30 gets 200 points because he was the fastest (I hope it's fair).
Thanks again everybody.
0
 
LVL 16

Expert Comment

by:Rick_Rickards
ID: 20394991
Just glad you got the answer you were looking for.

Rick
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening.  This article shows how to create and use them.
AutoNumbers should increment automatically, without duplicates.  But sometimes something goes wrong, and the next AutoNumber value is a duplicate.  This article shows how to recover from this problem.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question