84 minutes ago: I made a few modifications to the website yesterday so if you see any JavaScript errors let me know. Thanks.  Dismiss
Free Lessons
Fast Tips
Topic Index
Home   Courses   Templates   Seminars   TechHelp   Forums   Help   Contact   Join   Order   Logon  
Home > Courses > Access > Beginner > B1 > B1 Lessons B2 Lessons >
Back to Access Beginner 1 Lessons    Comments List
Data Normalization Upload Images   Link   Email  
Roland Richon 
2 years ago
Hello all
The CustomerT table contains a lot of data/fields. My question is:
1) what determines you put the complete data in one table?
2) what determines you split the data in several tables (normalization)?
Thank you in advance for sharing your experiences
Kind regards,

Scott Axton
2 years ago
The short answer is that there are no hard and fast rules.  In general, you only want your tables to deal with data specific to a single subject with supporting data in a related table.

See the Normalizing Data video.

You can also get Too Many Tables which is not good either.  See that link as well.

You just have to find a balance that works for your particular situation.
Roland Richon
2 years ago
Thank you Scott for your fast reply. Actually, I am watching the suggested "Normalizing Data" video :) and I will have a look to other suggested video also.
Well yeah, as you said you need to find a balance that works for one. And as Richard says, Access is like a Lego, there are multiple ways to achieve something.
I was just wondering if my current approach is ok as I tend to create for ex. tblPerson containing all the basic information such as FirstName, LastName, dob, pob a second table storing the addresses seperately tblAddress and maybe a third to store phone numbers, email etc. Of course the table are all related. Well I must assume this may look somewhat confusing, but I was adopting this apporach beacause of the normalization an keeping the tables as small as possible. Well I certainly need to find a middle-way and get more acquainted with this subject. Exchanging with others helps as well. Kind regards,
Adam Schwanz
2 years ago
Personally, I keep address and phone with the customer information, I try to use as few tables as makes sense. That too many tables video Scott linked is good. The only time I don't keep them together is when they need to store multiple address/phones and then I have to use more than one table. Like you said though there is a million ways to get to the finish line in Access and something small like this isn't going to sink the ship ;).
Richard Rost
2 years ago
It's mostly what works for YOU. My goal is to show you alternatives. If you need 10 different phone numbers for a client, then put it in a different table, like my ABCD does. If you need home, work, and cell, then you can stick it all in the CustomerT. Generally my rule of thumb is if you need more than 3 of anything: different table.
Roland Richon
2 years ago
thanks a lot to you all. your recommendations will surely help me. Greetings from over the great pond :)

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


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

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

Copyright 2024 by Computer Learning Zone, Amicron, and Richard Rost. All Rights Reserved. Current Time: 2/22/2024 1:49:31 PM. PLT: 0s