Also uploading an example of the calculation for the field on Divelog
I'd recommend a very different data model for managing your groups:
Divers::_pkID_Divers = Diver_Group::_fkID_Divers
Groups::_pkID_Group = Diver_Group::_fkID_Group
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained
Thanks for the recommendation. I implimented the notation into my table structure as a test, but I'm at a loss for how to set up the data entry layout to mimic the one from the my first screenshot (on the left) using this structure.
The intended data entry process: New Record, create a group name, identify the Divers, start logging dives.
My brain might just not be working on this, but how do you establish the join relationship for 2 or more divers from a single layout?
how do you establish the join relationship for 2 or more divers from a single layout?
You use a portal. A portal to Diver_Group on a Groups layout can be used to select each diver for your group.
That get's you to the fiirst few parts of your work flow. The challenge then becomes setting up a means of logging data in the DiveLog for each diver. I can think of a number of ways to set that up, but not being a diver myself, I'm not fully clear on which method would be best.
One option would be to set up a fields from an occurrence of DiveLog that Matches to Groups by a field in Groups. Clicking a row in the portal to Diver_Group performs a script that sets the field to the value of the Diver's ID. That would use a relationship such as:
Groups::SelectedDiverID = DiveLog|SelectedDiver::_fkID_Diver AND
Groups::pkID_Group = DiveLog|SelectedDiver::_fkID_Group
Select "allow creation..." for DiveLog|SelectedDiver in the above relationship.
A button in the portal would then use this script to set up the match fields for logging the dive:
Set Field [Groups::SelectedDIverID ; Diver_Group::_fkID_Diver]