You appear to have this relationship:
Tourer::__pkTourerID = Member Tours::_fkTourerID (though your field names are likely different from mine)
You can create a new table occurrence of member tours and link it to tourer like this:
Tourer::_fkSelectedTourID = Member Tour|selected::__pkMemberTourID
Then you can place fields from Member Tour|selected on your layout and a button in the portal row can perform this script:
Set Field [Tourer::_fkSelectedTourID ; Member Tour::__pkMemberTourID ]
to cause those fields to display data from the selected record.
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained
That worked well! The only problem I have now is that I can no longer add records using the portal. I made sure the relationship allowed adding records, but somehow making the field a button prevents me from adding more tours in the portal. Any ideas what I did wrong, or how to fix that?
Don't make the field a button. Put a button in the portal row next to the field.
EXCELLENT. That worked.
One more question regarding this. I have my portal rows and created a button; I used an arrow, on the side (for each entry) that when clicked, will update the fields in the rest of the layout. I also have WorkingTourCode populated in red when an arrow is clicked, so at a glance the user can see for which Tour the fields are displayed. I created a button from that field that when clicked, will bring me to a Related Record in a different Layout. This all works really well. I found a bug though when testing. If I click the TourCode field in the Portal (not the arrow button next to it), it will highlight it, and it seems to "set" my WorkingTourCode to that tour code - even though the text is not updated, as it is when I click the arrow. If I then click the WorkingTourCode field (button), it brings up the related record corresponding to the "highlighted" portal field - not the record for what the text is showing. I'm wondering why just clicking a field in the portal is "setting" my WorkingTourCode field to the value from the portal, hence displaying the incorrect Related Record in the other Layout.
I hope I described that well enough.
When you use GTRR to go to the portal's table occurrence the record in the portal that has the focus becomes the current record in the found set thus produced on the target layout. Clicking a button does not change the focus so the cursor in the portal row's field sets up that record as the current record in the target layout.
But it would appear that the button outside the portal is specifying the wrong related table. Set its script or script step to GTRR to the MemberTour|Selected "Table" instead of MemberTour. (Throughout FileMaker, you'll find drop downs where you are asked to select a table when you are really selecting a table occurrence--a box on the relationship graph instead of a table named as such in Manage | Database | Tables. )
Phil, I have to say, you amaze me. Though the drop down didn't show the "Selected" Table, in the field in the pop up for GTRR I didn't have the "Choose Records from" correct. I did have the original table, not the "Selected" table.
I really hate to feel like I'm taking advantage of you, but I do feel that way. Thank you SO much…. again.