Morning Rain, I am still struggling to work out the benefits of this design. For the unknowing user I still prefer my original design --> using frmMainMenu select client from combo, if the client does not exist click the button to create new or if you want to edit client click edit current button (this also works well for Sites, contacts, inspections)
There is no other information at this time that needs to be directly associated with client besides contact infomration, so nothing more required in the table.
Yes there is one main client contact and then many client contacts for different sites.
In frmMainMenu this has been allowed for by adding a checkbox to the frmContact (available from frmClients and frmMainMenu) that indicates whether this is the Client's main contact
Site also works well in my current design, maybe the only thing that is a little complicated with the clients, sites, contacts relationships is adding/ associating a client with a site, do you see a better way to do this? If I change my Junction design to have a single junctionID primary then I need to re-code the linking as I used a compound key originally
What should we do now?
Thanks