Re: Normalizing (and fixing) a large, messy DB
Alright, screenshot attached for latest relationship layout. Guides can work for more than one company, so the linking table is added. TblClimbers got adjusted too with how it links to tblGuides. I also added a linking table between tblPermits and tblRoutes, so we can choose multiple routes per permit.
tblPermits has fewer fields, but that is a good thing. I was thinking of Mark's earlier advice regarding how to indicate that a climb was led by a guide. The "ClimbPurpose" is a lookup field which includes several options, one of which is commercial guide. That should be adequate for later determining which climbs were guided, no? I also eliminated the "number of climbers" field, because that should just be calculable data I get from my other tables.
Any additional thoughts?