If this helped, please click the star at the bottom left of this posting and add to my reputation . Many thanks.
Bob Fitzpatrick
Yeah, that's another option I'm considering. Thanks for the tips.
Then you have to create an additional table and form to specifically register documents attached to invoice. I.e. you have e.g. table tblInvoices, table tblProducts, tblInvoiceProducts, table tblTaxDocuments, and table tblInvoiceTaxDocuments. And the invoices form has 2 subforms - one for invoice products (product rows), and another for invoice documents (document rows).
Or, as was adviced, you have a invoice FK field in your tblTaxDocuments, and skip the need for additional subform entirely. The only problem with this is, that probably the tax documents are registered much earlier than invoice, so you (or user) has to remember to link the invoice key to tax documents after the invoice is registered. I.e. user registers invoice, then activates tax documents form, locates all documents there to be linked to this invoice, and creates the link for every one of them.
Thank you, I actually thought of the junction table as well, but I thought it was a bad database design, trying to represent a 1:N relationship as a M:N. Or is this a reasonable thing to do? Maybe all I need to do is limit the number of entries in the junction table via code.
Please review the attached sample.
Cheers,
@Thomasso: have you had a chance to review the sample I uploaded, does that answer your question?
Cheers,
Hi Vlad, sorry for replying so late, I am a bit busy.
Yes, this works well for me, thank you very much! :-)
Tomas