Microsoft Access DB with multiple users


I am using Microsoft Access 2000 to create a rather large database(by my standards).  The database will sit on my network. Up to 16 people could be using the databas at any given time.  Will this pose a problem?  I need the database to run flawlessly or as close to it as possible.  I was considering breaking up the database into 3 and having only about 4-5 users at any given time.  I know the database can handle the number of users on paper but I would rather have input from someone with real life experience.  I don't want to take any risks!!!

Here are some specs on the size of the database...if that makes a difference.

It has a main form and about 4-5 subforms.  There are about 400 records in the main form and each related subform contains about 60 records.  When I complete  a large query I am near the limit of 255 columns.

Thanks Jim
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.

It depends on how many concurrent users you have, and how many concurrent updates and edits they will be carrying out. Is there a significant risk of users editing the same record at once?

If most of the user are reading and not editing records, you should be ok.
first you should strongly consider 'splitting' the database into a Front-End,with all the forms, reposts queris etc and LINKS to the Data tables whkch are REAL tables in the Back-End.  There is Wizard in Access that can simplify the process for you.

This is actually a rather small database. I built an app, a couple of years ago, that had several thousand records, and several forms, and multiple reports, and about 50 potential users, and NEVER had any corruption issues (just lucky I guess, or so I have been told).  This was split into the FE-BE model that I mentioned above.

AW, was that an mde or mdb front end? I'm told that mdes are far less prone to corruption as well - I've never really used them except for small standalone dbs as I tend to make use of some features that don't work in mdes.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

jdolan2587Author Commented:
Thanks for your quick response.  

All users will be making edits but it is unlikely that they will be editing the same record.  

I have created the datbase for elementary report card grades so in most cases only one teacher will be editing his/her class (25 records or so).  In some cases there are 2 or 3 teachers but it is unlikely they will be working on the same student or record at the same time.

For some reason I feel more comfortable breaking the database up into 3 seperate identical databases but I don't want to make more work for myself in the end if I don' have to.  I know that this is not the proper use of a database but my advanced database knowledge is limited.  

I am unfarmiliar with front end and back end design.  


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
Shane, I have never used MDEs - to many headaches when changes to the FE need to be made.  

Jim, there is nothing to 'design' - you simply treat the SINGLE MDB as normal, except that the REAL tables are physically located in the BACK-END and linked to the Front-End which has ALL of the Froms, Reports, queries etc.  The FE behaves EXACTLY as if this were a SINGLE database.  There are no design 'issues'.  YOu build the app as a SINGLE mdb, and at the very end, before giving it to the uers, run the DataBase Split wizard, and there you are.

Once you understand the process, you can the n BUILD the MDBs from scratch, as a split App, but that is for more experiences developers.  Most of the time, the easiest appraoch is to SPLIT as the last step in the development process.

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.