Hi Richard,

I can verify your result. I even remember, but can't find, a discussion 
of this from a number of years back.

I recall from those discussions that the right hand table of a 
relationship must be an indexed field, but perhaps this isn't as solid a 
rule as I remember. You've used a global, which can't be indexed, but 
seem to have achieved the same result as the 'x' comparative operator (I 
forget the proper name) in your relationship. An interesting side fact 
is that you can use 'Allow creation of new records in this (your 'B') 
table'  for your relationship and this can't be done with the 'x' join.

Still, it looks like you really want the 'x' join. This will eliminate 
the need for the global field 'B:ASeq Socket' and keep your tables cleaner.

Mike



On 30/01/11 7:57 PM, Richard S. Russell wrote:
> On 2011 Jan 30, at 18:42, Bruce Herbach wrote:
>
>> Hi Richard,
>>
>> I have set this up for a number of layouts and it usually works. Frequently I have used a script with a button or script trigger to change the value of the global field so that as I change records, the portal shows the related records. Is it possible that you are triggering an update to the global? Have you looked at the global with the data viewer to verify that it has the correct value?
>
> I have the global value "B::ASeq Socket" displayed in the body part of Table B. There are 12 records in Table B, and each of them shows "1" as the value of "B::ASeq Socket" when I click the appropriate button in Record #1 of Table A. When I go to Record #2 of Table A and click the same button, all records in Table B show "2" for "B::ASeq Socket". When I turned off global storage for that field (thus clearing the value in it) and then turned it back on again, all Table B records showed the field as empty.
>
> Nonetheless, regardless of the value in that field (including none at all), every single record in Table A still shows me a portal displaying all 12 Table B values.
>
> If anyone's interested in examining this in more depth, I'd be happy to share the file. It's tiny. Contact me directly at [log in to unmask] to get a copy of your very own.