subform with two functions.

[erich_18]

Good Day Everyone,



I'm trying to figure out how to have 1 subform perform various tasks.

in the parent form (frmInvoiceHeader) the user enters the invoice headers, which is the information on an invoice that does not need to be repeated per item (such as invoice date, invoice number). the information entered is saved in the tblInvoiceHeader Table. the InvoiceNumber is the primary/unique key. The parent form's record source is tblInvoiceHeader

in the parent form I added a subform (subfrmInvoiceDetails) in datasheet style. the user then inputs data in the subform. this data is saved in another table called tblInvoiceDetails. the subforms record source is tblInvoiceDetails.

there's a one to many relationship between tblInvoiceHeader and tblInvoiceDetails via the InvoiceNumber.

up to here everything works fine. the information added in the subform is related with the invoice number created in the Invoice header form. I used a query to verify this and when I look up the invoice number (from a combobox selection on the parent form) it shows all the items (in the query) the user entered in the subform.

the combobox's (in the parent form) row source is set to InvoiceNumber from tblInvoiceHeader.

the combobox is unbound.

what I would like is for the user to be able to select an invoice number from the combobox and all the records related to that invoice number is populated in the subform. but not only to see the data but also to edit, delete, add new items if needed.

its like going back to a previous invoice to browse and make changes if needed.

is it possible to have a subform perform these 2 tasks? 1. query and 2. edit, update, add, delete..etc)

attached an image of my form and an image of the query results from the combobox selection.



and the invoice number relationship



tks.

Eric

[Micron]

Are you saying you cannot append or edit details? From the fantastic description/details you've provided, it seems you've done everything correctly and should be able to do so. There would of course, be some exceptions, such as if the forms were based on queries that are not updatable, you opened the form as read only, or the form records were based on a snapshot recordset. I'm not seeing any evidence of those things. The design view of the query may have been better, rather than its datasheet view because it seems you based main form on a table and the subform on a query. The query may be the problem if you can't update or append to the form. In that case, I'd open the query itself to see if it's updatable. If not, then that's the issue. If it is but the form is not, then there's some other issue.

[davegri]

Your descriptions of the forms and table names do not match the images you provided, so it's hard to make any analysis. Your description is viable, but the images don't reflect the words.