JoeBruce,
Looking through you data, you may be able to drop the "TblGuides" entirely. You have a field "IsGuide" in tblClimbers. If you replace this with GuidCompanyID, this will mean that the climber is also an employee of that company.
If the climber can be a guide for more than one company, you'd want to use the same type of table as "ClimberRecords" to link a climber to one or more companies.
This also means that in your "ClimberRecords" you can have a an "IsGuide" field there to indicate that, for that given climb, they are a guide.
This means that when you look at permits you will see all of the climbers on a permit AND see who is a guide for that given permit. Unless someone can change between being a climber and guide DURING a climb, this should model what you are looking for when you attach climbers to permits and want to indicate who's guiding them (if anyone).
Looking through you data, you may be able to drop the "TblGuides" entirely. You have a field "IsGuide" in tblClimbers. If you replace this with GuidCompanyID, this will mean that the climber is also an employee of that company.
If the climber can be a guide for more than one company, you'd want to use the same type of table as "ClimberRecords" to link a climber to one or more companies.
This also means that in your "ClimberRecords" you can have a an "IsGuide" field there to indicate that, for that given climb, they are a guide.
This means that when you look at permits you will see all of the climbers on a permit AND see who is a guide for that given permit. Unless someone can change between being a climber and guide DURING a climb, this should model what you are looking for when you attach climbers to permits and want to indicate who's guiding them (if anyone).