[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Microsoft Access DB with multiple users

Posted on 2004-10-21
6
Medium Priority
?
1,156 Views
Last Modified: 2008-03-17
Hi,

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
0
Comment
Question by:jdolan2587
[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
  • 3
  • 2
6 Comments
 
LVL 41

Expert Comment

by:shanesuebsahakarn
ID: 12369254
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.
0
 
LVL 44

Expert Comment

by:Arthur_Wood
ID: 12369782
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
0
 
LVL 41

Expert Comment

by:shanesuebsahakarn
ID: 12370141
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.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 

Author Comment

by:jdolan2587
ID: 12371259
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.  

Jim
0
 
LVL 41

Accepted Solution

by:
shanesuebsahakarn earned 375 total points
ID: 12375125
0
 
LVL 44

Assisted Solution

by:Arthur_Wood
Arthur_Wood earned 375 total points
ID: 12377041
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.

AW
0

Featured Post

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.

Question has a verified solution.

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

In Part II of this series, I will discuss how to identify all open instances of Excel and enumerate the workbooks, spreadsheets, and named ranges within each of those instances.
Did you know that more than 4 billion data records have been recorded as lost or stolen since 2013? It was a staggering number brought to our attention during last week’s ManageEngine webinar, where attendees received a comprehensive look at the ma…
In Microsoft Access, learn how to “cascade” or have the displayed data of one combo control depend upon what’s entered in another. Base the dependent combo on a query for its row source: Add a reference to the first combo on the form as criteria i…
In Microsoft Access, learn how to use Dlookup and other domain aggregate functions and one method of specifying a string value within a string. Specify the first argument, which is the expression to be returned: Specify the second argument, which …

656 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