On 2011 Jan 30, at 15:59, Jonathan Fletcher wrote: > Russel, > > Your original message said that you are using a global field for the parent > side of the relationship. What happens if you turn off global storage on that > field? I'm sot sure what you are doing exactly, but that seems like it would > cause the behavior you describe.
Turning off the global storage for B::ASeq Socket produces empty portals for every record within Table A. Furthermore, turning off global storage erased the contents of B::ASeq Socket, so it was empty after I reverted it back TO global storage, and I STILL got 100% population of Table B records in the portal for every record in Table A, even tho there was nothing at all to connect to in Table B. I keep thinking there's gotta be some way I can turn this into a source of free energy (look! something from nothing!) and make a bazillion bux, but really I just want it to go away and behave the way I think it should.
