Building Input Form Based on Two Tables

[tx_developer]

Hi,

It has been a very, very long time since I have used MS Access. I am building a small database and form for a friend and now can't seem to remember how to do things.

I have two tables - CLIENT and SESSION

CLIENT has client_id plus name, address, phone, etc.
SESSION has session_id, client_id, session_date, price

I have a one-to-many join between client and session.



This application will have several forms and one of them is for entering any time a client came in for a session and how much they paid. On this screen or form I want to display the client's name (rather than the ID of course) and let the user input the date and price paid. For some reason I cannot remember how to do this.

Would I create a query with the fields I want and make it an update query? If someone could point me in the right direction I would very much appreciate it.

Thank you,
tx_developer

[pbaldy]

Typically a one-to-many relationship is handled with a form bound to the one table containing a subform bound to the many table. Master/child links keep them in sync with each other.

[Missinglinq]

As Paul has suggested, a Main Form/Subform is the way to go, here:

1. Make a Form using the CLIENT Table
2. Set its Default View to Single View
3. Make a Form using the SESSION Table
4. Set its Default View to Datasheet View
5. Open the Client Form in Form Design View
6. Place a Subform Control on the Form
7. When the Subform Wizard comes up, select the Form based on the SESSION Table for its Source Object
8. 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)>

[tx_developer]

Awesome...thank you both. I am on the right track but have one issue. The SESSION table also has a package_id from you guessed it, the PACKAGE table which has things like Groupon, Living Social, and other packages. I created a drop down (or combo box I guess) to display the package name. When I drop down and select a package for one session record, all the other session records are set to the same package name. When I created the combo box with the wizard, if asked at one point if I want Access to remember the value. Not sure if that's why it is doing this or not but now I can't find how to change it.

Thanks,
~TX

[Missinglinq]

The Combobox for Packages needs to be Bound to a Field in the underlying Sessions Table, in order for it to be Record-specific.

Linq ;0)>