Synchronizing multiple Portal navigation

[mickeyfinn]

This would solve a problem I'm having with a layout the customer wants to see. I have a "ticket" layout which shows a number of child records (pages) for each ticket record. There are about 3 portals with exactly the same table occurrence relationship each on a different tab of a tab object. My customers use fmp 8 so no object naming. I am trying to find a more effective way to have portals show the correct page without the risk of one showing page 3 whilst the other is still showing page 1.

I have scriped nav buttons which essentially go to a field on each tab and then move to the portal row number which works, but looks "clunky" especially on slower computers.

Also, while I have one portal showing an overview of pages (up to 10), all the rest are single row portals. In order to allow them to move to different rows, I seem to have to include the scroll-bar, which I don't want to show or allow access to. I've tried hiding it but the user can accidentally press it and get a layout which shows half one page, half another. I tried putting objects in front but you can still click it through another object. Ideally I'd like to have the user highlight a row in the overview portal and have the others navigate accordingly. I could use buttons in each row to do this but I thought there may be another way since there are editable fields in this portal. Is there a better way?

[Matthew F]

It would be nice if the Get(PortalRow) function worked well in calculated fields instead of just scripts. Then you could just use this as a match field and display the related result in real time without the need to scroll a one row portal.

Is your scripted solution still too clunky if you specify Freeze and Refresh Windows at the start and finish?

[mickeyfinn]

It's certainly cleaner looking using Freeze/Refresh, but I still have the invisible scroll bar that will scroll if accidentally clicked on. Why does Get(PortalRow) not work without the scroll bar?