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 36 days 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.
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 36 days 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 36 days 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 ;).
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 36 days ago
thanks a lot to you all. your recommendations will surely help me. Greetings from over the great pond :)
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.