Re: Asking too much?? Form-subform based on 4 tables, one is a junction table.

Tech-Archive recommends: Fix windows errors by optimizing your registry



No replies? Anybody? Suggestion? Comment?

-Sam

Sam wrote:
I have a problem with creating a form from tables involving a junction
table. What I learned from this group is: Create a form based on one
one-table and a subform based one many-table, and have the combobox in
the subform be based on query on the-other one-table.

My situation:

tblCustomer one-many tblSales
tblSales one-many tblReceipt_Allocation
tblReceipt one-many tblReceipt_Allocation

One receipt from a customer can be used to pay more than one invoice.
And one invoice can be paid by more than one payment/receipt.

I have created a form frmReceipt (recordsource: tblReceipt) and a
subform fsubReceipt (recordsource: tblReceipt_Allocation).

In the subform, a combobox is used to pick out invoices that will be
paid. Then the user will enter the payment amount for each invoice,
manually splitting the payment amount (tblReceipt doesn't have a field
for total receipt amount).

Currently this combobox is not filtered by customer. Instead, it will
list all open/not fully paid sales. So, a payment can pay for sales of
more than one customer, which isn't right.

What I would like the user be able to do when receiving a payment is:
Open a form, pick a customer, enter payment info (date etc.), pick from
a list of open invoices, allocate the payment to one or more invoices.

Could somebody please help. Thank you in advance.

-Sam

.



Relevant Pages

  • Re: Subforms....Advise Please...........
    ... Customer => Payment ... visible property of each form so at any one time only the main form controls ... info subform in it and create two separate data entry forms for the other two ... The normal usage is 2 tables with a one-to-many relation, such as Invoice ...
    (microsoft.public.access.forms)
  • Re: Subforms....Advise Please...........
    ... customer this is when they are on a secondary tab page. ... info subform in it and create two separate data entry forms for the other ... line items for the invoice.) ...
    (microsoft.public.access.forms)
  • Re: Subforms....Advise Please...........
    ... Customer => Payment ... What property would I set to make the subform frames merge with the main ... The normal usage is 2 tables with a one-to-many relation, such as Invoice ...
    (microsoft.public.access.forms)
  • Re: Subforms....Advise Please...........
    ... You might like to try the tab control, ... The only issue is that the user can't see which customer this is when they are on a secondary tab page. ... info subform in it and create two separate data entry forms for the other two ... >> The normal usage is 2 tables with a one-to-many relation, such as>> Invoice ...
    (microsoft.public.access.forms)
  • Re: Business objects, subset of collection
    ... FOREACH invoice IN invoiceSet ... FOREACH payment IN paymentSet ... you are going to have to provide unique access because the mappings are not the same as in the RDB schema. ... about solving specific customer problems. ...
    (comp.object)