You will need more than 3 tables. What I'm seeing is
- tblInsCo (Insurace Companies as a 1 side table; that is, no dupes)
- tblInsCoLoc (many locations to 1 insurance company; i.e. repeating CO ID's per location)
- tblLocConts (many contacts to 1 insurance location; i.e. repeating LOC ID's per contact)
- tblTruckCo (Trucking Companies as a 1 side table; no dupes)
- tblTruckInsCo (many Insurance Companies to 1 Trucking Company; i.e. repeating Truck Co ID's per Ins Co.)
EDIT
Forgot to mention that if I have this right, it would be the bare minimum. You might want lookup tables to control input. An example would be lookups for companies so that user cannot arbitrarily add their own or misspell a company name when creating a new association between that company and an additional location or contact. Don't confuse my mention of lookup tables with lookup fields. They are not the same thing.
Last edited by Micron; 11-21-2018 at 04:32 PM.
Reason: added info
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.