Originally Posted by
orange
...If there is only 1 address per voter, then 2 tables may not be necessary. I'm not following the VoterAddress table, if voter to address is a 1 to 1 relationship...
I agree! We often speak of a database being Non-Normalized...but on the half-a-dozen forums I travel through, each day, I see a fair number that are what I call Over-Normalized, and being so designed causing their developers all kinds of unnecessary problems! The general rule is that if their is only one entry for a given piece of data, i.e. you'll only record one address per voter, that Field should be in the same Table as the voter name...ditto for phone number. You'd only need a separate Table for addresses if you want to record multiple addresses per voter.
Last week I saw a post (elsewhere) where the poster was doing a fast and dirty db for a class re-union. He was only recording name, address, phone and attending/not attending...but had separate Tables for
Classmate Name, Address, City, State, Zipcode, Phone Number and Area Code!
And, being a novice, was completely overwhelmed when trying to pull up a classmate's record by retrieving data from seven Tables!
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007