Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multiple Access User Question

Status
Not open for further replies.

firebirdta84

Technical User
Aug 23, 2007
56
US
I am building a database for a group of 45 people. These people will use this database to enter information on a daily basis. Some questions I have:

1. Should I put the database on a shared drive and have everyone access that one file, or should I "split" the database and put the "data file" on the shared drive with the interfaces saved on each individuals computer?

2. Is there a limit to the number of people who can be using the database at the same time for either of the options listed above?

Fairly new to Access, so please bear with me...

Thanks,
Joe
 
You must split the database and put the data on the server and give each person their own front end.

"The maximum number of concurrent users that the Jet database engine supports is 255"

However some people would say that you would be better moving to a different database if you intend to have this many users, others would disagree.

You may wish to read faq700-184.
 
Also you may want to consider that Jet is a "file server" database engine. If a user has a query with three tables, all the tables data is sent across the network. With 45 people, this is alot of traffic. You may want to check out the MSDE engine. It's a client/server database engine. A request is sent to the server, the query is then processed and only the result is transferred across the network. Obviously less network traffic with 45 people using it. MSDE is called a Microsoft Access project. If you can develop in Access, it's not that much different.
 
A key question is how many do you think would be using it at the same time?

Personally, 45 sounds like too many (at the same time, at least). Especially if you don't have much experience with Access.

 
It also depends a great deal on what the users will be doing, not just how many users there are.

If the majority of users are merely inputting new records 45 may not be a problem. If all 45 users are regularly running queries 45 may be an issue.

I've had systems primarily used for data entry with well in excess of 80 users with no problems.

Ed Metcalfe.

Please do not feed the trolls.....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top