Hi, Terry.
As I understand it you are in one of the following cases (my guess is the third):
You have a table storing invoices (One side of the relationship) related with another one keeping invoices details or some other related info (many side).
- Case 1
You want to have a form showing ONE invoice number and a subform in it showing ALL the related info.
The approach proposed by Carol is the good one (parent form/subform related through master field(s)/child field). It is generally meant to allow visualization and edition of data.
When you switch from one invoice to another one using the records selector of the first form ,records (details) are automatically updated in the subform. You CANNOT have various invoices on your first form and all the details related to each of them in the subform, since the form/subform is meant to show the results of a ONE (invoice) to MANY (details) relationship (you can eventually show various invoices, but only one is active and determines the children records shown in the subform).
An alternative to the record selector for this would be to make a select box on the first form which would allow the user to choose one invoice and have both forms update accordingly (ACCESS has a wizard to build such a select box)
- Case 2
What you may want to do is perhaps have a list box with invoices on a first form and based on what the user selects (eventually various invoices), show the related details. This is generally meant only of vizualization .
You do not need to link your form/subform for this, but a bit of programming. If this is what you want to do, re-post and i will give you further details.
- Case 3
You have a form, a subform showing various invoices, and you would like a sub-subform to show the related details. This is a bit too much to show and manage at the same time. Consider splitting into separte forms:
A form + subform showing the invoices. Then the user can select an invoice, and click a command button on the subform that opens a new form showing the related invoice details.
Again a bit of programming is needed in this case.
Note: Be carefull with terminology, so that we can understand and help you more easily (ie: what relates to sets of records or two tables are fields (in your case: the invoice number...))
Hope this helps.