AllExperts > Using MS Access 
Search      
Using MS Access
Volunteer
Answers to thousands of questions
 Home · More Using MS Access Questions · Answer Library  · Encyclopedia ·
More Using MS Access Answers
Question Library

Ask a question about Using MS Access
Volunteer
Experts of the Month
Expert Login

Awards

About Us
Tell friends
Link to Us
Disclaimer

 
 
 
 
About Scottgem
Expertise
I can answer almost all types of questions relating to Microsoft Access usage and application design. My strengths are database and interface design.

Experience
I've been designing databases for over 15 years working with dBase, FoxPro, Approach and Access.

Organizations
Author of Microsoft Office Access 2007 VBA
Techncial Editor for Special Edition Using Microsoft Access 2007 and Access 2007 Forms, Reports & Queries From Que Publishing

 
   

You are here:  Experts > Computing/Technology > Business Software > Using MS Access > New Project added to old

Using MS Access - New Project added to old


Expert: Scottgem - 11/6/2009

Question
Good morning Scott. I have a database that is complete in Access 2003.  My boss wants to add a new category to it.  This new project if you will, has a lot of the same information as the already existing database. Since I have not had a lot of training in Access, I'm not sure how to go about this.   My initial thought is this.  1. Add to existing tables, making new tables as needed. 2. create a form to add the data. 3. Add this category to my main forms index.     Or   Should I create a brand new database with all new tables ect.  If I do it this way, how would I get the same information from both databases on the same report?
We will be adding other products also, this is just the second one but I want to do this correctly.   does this make sense?

Answer
You should never use tablenames (or even fieldnames) to define data. If your database had been designed using best practices initially, you wouldn't be asking this question. I'm not putting you down, by the way, just trying to explain the best way to handle this.

You should have a Projects table that contains information specific to a project. Each project record is then assigned a primary key. You then include that primary key as a foreign key in the related tables. If there is information that is unique to a specific type of project you can then add another table for each type of project just to store that specific info. For example, I built a database for a client that is an insurance broker. There is general data applicable to all policies, but there is also info specific to types of policies. So I have a Policy table and then tables for each type (i.e. Health, Dental, Diability etc.) that is related on a one to one relationship with the Policy table on PolicyID.

So, you see if you had created a Project table in the beginning adding a new project would be as simple as adding a new record in the Project table.

Hope this helps,
Scott<>
Microsoft Access MVP 2007
Author: Microsoft Office Access 2007 VBA

Add to this Answer   Ask a Question


 
User Agreement | Privacy Policy | Kids' Privacy Policy | Help
Copyright  © 2008 About, Inc. AllExperts, AllExperts.com, and About.com are registered trademarks of About, Inc. All rights reserved.