In 13. You could possibly create pile of tabs with a variable as a name and reduce the padding so they repeat to the smallest size possible, and hide all the fields on that tab of the variable was not set.
Then the tab would grow when the name in the variable was set...
Create approval to the related collection records, then show only the first row on tab 1, the second on tab 2 etc.etc.
If your data structure looks like e.g.
Streams --< Collections --< Catches
you could use fake tabs by adding horizontal single row portals into a Collections relationship driven by a utility field, with a different initial row; “switching tabs” then means actually switching the collectionID, and thus the displayed related Catches records.
This obviously needs a certain number of portals set beforehand, but then the number of tabs in a tab control cannot be changed programmatically, either.
What I would like is that I could give them a button that has a Script trigger
Just to confuse the issue : if you define a button, you don't need a trigger – a button is defined as an object that has an “OnClick” trigger (though that event type isn't (yet) named anywhere in Filemaker).
Yes, I have 13.
Would it work to have a Portal inside of another portal? I can't figure out how to do a popover inside of a popover.
Yes, the structure is Streams --< Collections --< Catches
Sorry about the script trigger button thing. I've only started with Filemaker a week ago.
There are certain containment objects that you cannot nest in each other. You can't put a portal inside another portal. Same with pop-overs. There can only be 1 active/open pop-over at a time.
And you can't get around any of these rules by hiding them in another containment object. For instance, you can have a portal in a pop-over… but not if that pop-over itself is already in a portal.
See here for a sample file outlining the idea suggested in my post.
Actually, two approaches – one using a tab-like series of portals, another one a vertical portal. As usual, there are other solutions, but the optimal one probably depends on your workflow / the amount of collections you want to record for any given stream.
WhatsTheCatch_eos.fmp12.zip 71.9 K