short how?
It's a good article and I agree with pretty much everything the author states
my variations include using plurals for table names and instead of prefixing with 'tbl' to tell me it is a table, I use for example 'dta', 'lst', 'jtn', 'tmp' etc to tell me what type of table - data, list, junction or temporary
if you take out the examples you are left with what to do - but new users generally blithely ignore such advice because they don't see why it matters, or perhaps it's one step too far in their initial steps on the development road.![]()
I agree with you that new users to database design don't want to read that article. Their eyes roll back in their head when you mention data normalization. Beginners to database development just don't know enough to see the benefits.
Microsoft releases Access templates that are not properly normalized or follow good naming conventions. I can see how that only makes articles on naming or normalization seam not very important.
Boyd Trimmell aka Hitechcoach
Database Architect and Problem Solver
Microsoft MVP - Access Expert
25+ years specializing in Accounting, Inventory, and CRM systems
"If technology doesn't work for people, then it doesn't work."