Just make sure that id2 is a primary key in the parent B table. Join A should have a combination of two foreign keys, one from A and one from B.
Sure, Thaks Nicolai.
If displaying related records (in a portal, for example), you *can* use fields more than one relationship away.
'Parent A' has:
'Parent B' has:
'Join A' can have:
This allows you to SEE (from Parent A, for example):
Betty shows James and Edward
Doris shows James
Ann shows Bob and Edward
(and the reverse is true is seen from Parent B):
James shows Betty and Doris
Bob shows Ann
Edward shows Betty and Ann
On *both* of these layouts the same portal is used with the relationship to 'Join A' (matching appropriate fields on the RGraph, of course).
You can add other fields in the Join A table (if any) to the portal, but mostly you want to show the relationship to the respective other parent table. Same portal relationship, different fields based on the direction of the other table.
Does that make sense?
In the same way, you can show (Customers->Invoices->InvoiceItems) all invoice items a customer has even though it's two relationships away. Only for that you can directly select the InvoiceItems for the portal relationship. It will respect that it's going _through_ the related invoices (for that customer only).