Subject: | |
From: | |
Reply To: | |
Date: | Sun, 30 Jan 2011 14:04:19 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Here is a bizarrity I just encountered. In Table A I have an auto-entered sequence code (call it "ASeq") that uniquely identifies each record. Over in Table B are a dozen or so records that I'd like to show up in a portal in ONE record in Table A, so that I may pick and choose amongst them. So, within Table B, I create a global field called "ASeq Socket", and I plug "ASeq" into it to create a relationship.
Beautimus! Within Table A, I go to Record #1, click a button to insert the value "1" into "ASeq Socket", and sure enuf, all the values from Table B show up in the portal for Record #1, just the way I'd expect.
Now here comes the odd bit. I go on to Record #2 in Table A, and there they are still, all the Table B values in the portal, just as if I'd plugged the number "2" into "ASeq Socket" instead of "1".
How can this be? How can 2 = 1? (Yes, I guarantee that the relationship was an "=" sort, not an "X" sort.)
|
|
|