PlymouthSid
New member
- Local time
- Today, 10:08
- Joined
- Mar 13, 2025
- Messages
- 4
Thank you for that gentlest reminder of RDB basics ;-)When you have a set of data where addresses are frequently duplicated as with families and contacts at companies, the best solution is a separate Address table. That allows you to change the Address for a group of people at the same time. With your method, you need to change every family member's address.
In my defence I did say "I suppose I could have used a variation on the “Clients / Orders” design."
I was so pleased with getting all the other routine inputs based upon related tables (and combo boxes) that I quite failed to realise that the same logic applied to addresses even though most cases were be one-to-one not one-to-many! In truth, there are less than 200 members but the majority are "Couples") so I did miss that trick . . . . . doing things the right way always pays dividends.
It will be a simple enough task to correct that error and even better, it will keep me occupied whilst giving me a reason not to do gardening!