I have a portal on a tab control that is used by the client to select a job to display job details on another tab control. The client has asked to have the selected job in the portal on the first tab control remain visible after the find is completed and the page is once more displayed with the appropriate job detail information on the second tab control.

Filemaker's default behavior when the page reloads following the find request is to go back to the top portal row on the first tab control. I wrote a script to store the value of the portal row then go back to the portal row after the find request. The script works perfectly if the portal is not on a tab control. However, when the portal resides on a tab control, Filemaker changes tabs when I tell it to go the the portal row indicated by the globally stored value of the portal row. I named the tab control with a specific object name and added the script step to Go to Object "JobID" before going to the specific portal row but it still does not perform the procedure properly.

Edited June 24, 200916 yr by Guest

Try naming the portal itself with an object name and go to that object instead followed by a go to portal row.

Thanks so much! That did the trick!