As Paul has suggested, a Main Form/Subform is the way to go, here:
- Make a Form using the CLIENT Table
- Set its Default View to Single View
- Make a Form using the SESSION Table
- Set its Default View to Datasheet View
- Open the Client Form in Form Design View
- Place a Subform Control on the Form
- When the Subform Wizard comes up, select the Form based on the SESSION Table for its Source Object
- The Wizard should ask if you want to link the two Forms using the client_id Field; say Yes
Bob's your uncle!
As you move thru the Records in the Clients Form, the Records in the Sessions Form will display appropriately.
If you go to enter a new Sessions' Record, Access will automatically insert the client_id from the Current Client Record into that Record.
If you find you have a need for things like Command Buttons on the Subform, you'll need to set the Default View for that Form to Continuous, which allows buttons, instead of Datasheet View, which doesn't. You can then tweak the design of the Continuous Form so that it looks like a Datasheet, if that's the look you want.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007