I found a strange problem in FM7:
I have a table A, linked to B (child of A), linked to C (child of B).
In a layout for table A I put a portal with records from C. If I put
fields or buttons for table B in that portal, they will only refer to
the first matching B record!
I found a workaround: if I extend the chain with another occurence of B
(say B2), so I have A < B < C > B2 ("<" means 1-to-many relationship)
and put fields/buttons for B2 instead, it works fine. But why wouldn't
it work with B?

Adrian

You have found the proper way of setting this up. It doesn't work in
your original arrangement specifically because TableB is between A
(layout base) and C (portal). The valid relationship is from A to B,
but since the portal is not for B, it is treated as though you'd put
that 'B' field anywhere else on the layout and therefore shows the first
related record.

Since you are showing records in the portal from C, the B field grabs
the correct B record from the chain based on the context from which it
is coming from (A). I'm not saying it wouldn't be nice or logical for
it to show the correct B record since there is obviously a (potentially)
unique B record for each C...but that's just not how it works.


aditsu (AT) gmail (DOT) com wrote:
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg (818) 883-2846
FM Pro Solutions Los Angeles, California

FileMaker 7 Certified Developer
Associate Member, FileMaker Solutions Alliance

Oh, I guess I'll have to live with it then.

Thanks
Adrian