Free Lessons
Courses
Seminars
TechHelp
Fast Tips
Templates
Topic Index
Forum
ABCD
 
Home   Courses   TechHelp   Forums   Help   Contact   Merch   Join   Order   Logon  
 
Back to Access Forum    Comments List
Upload Images   @Reply   Bookmark    Link   Email   Next Unseen 
Desgin ideas
Roland Richon 
     
3 years ago
Hello people,

I need to create a contact db, but I am struggling a bit with the design and I hope you guys can give me some hints.
The db should content different kind of people like contact persons in different companies, compliance officers from financial institutes and also people from different public administrations where some people may hold a rank.

I was wondering, if I should put all this different people in one table like in the contact db from Richard, and to create separate tables for functions & ranks, and companies etc.? What do you think?

Thank you in advance for any suggestion.
Kind regards,

Roland
Scott Axton  @Reply  
        
3 years ago
Yes you want to keep all of the people in a single table. People are people.  Add in any descriptor for the people that would help describe them.  You don't have to use it if it doesn't apply.

See the Too Many Tables video.  That may help clarify things for you.
Scott Axton  @Reply  
        
3 years ago
Check out the Helper Data as well.  This one gives you a good way to store lots of data into one table rather that cluttering your data base with multiple little tables.
Roland Richon OP  @Reply  
     
3 years ago
Hello Scott, thank you for your swift response (at this late hour for you) and reminding me these videos. They slipped completely off my radar :) I will check them out and I will certainly find a suitable solution for my project. Technically it shouldn't be too complicated.

Another thing, what do you think about data modelling before setting up a db? Personally, I think it makes more sense when you create a more complex db?

Kind regards,
RR

Scott Axton  @Reply  
        
3 years ago
I'm a firm believer in data modeling.  Possibly not in the formal sense of the concept though.
My modeling is closer to the example that Richard demonstrates in the Association series.

I usually put down the information I need to gather (fields) and the relationships before I even start working with Access.  Once you have a road map before you it is much easier to get to the end point that you are wanting to reach.  Sure, there will be things you think of along the way that you have to adjust for. It is easier to do if you know where you are going.  Once you hit a road block you just reroute your path to the end destination.
Roland Richon OP  @Reply  
     
3 years ago
that sounds like a good approach, thanks a lot

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Access Forum.
 

Next Unseen

 
New Feature: Comment Live View
 
 

The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.
 

Learn
 
Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
Seminars
More...
Customers
 
Login
My Account
My Courses
Lost Password
Memberships
Student Databases
Change Email
Info
 
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Help
 
Customer Support
Web Site Tour
FAQs
TechHelp
Consulting Services
About
 
Background
Testimonials
Jobs
Affiliate Program
Richard Rost
Free Lessons
Mailing List
PCResale.NET
Order
 
Video Tutorials
Handbooks
Memberships
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Shipping
Terms of Sale
Contact
 
Contact Info
Support Policy
Mailing Address
Phone Number
Fax Number
Course Survey
Email Richard
[email protected]
Blog RSS Feed    YouTube Channel

LinkedIn
Copyright 2026 by Computer Learning Zone, Amicron, and Richard Rost. All Rights Reserved. Current Time: 5/1/2026 11:34:02 PM. PLT: 1s