I have on layout with a tab (2 tabs). If you put portals on the tabs and run a script from the non dominant tab, after the script is done, it always defaults to the first tab. Even if you put the portals outside of the tab but you are on the second tab, it still defaults to the first tab. This makes a yucky interface. Is there a way to control this?

I've been worrying about this also - which tab is the default. I think the answer is that the tab which is showing when you last exited layout mode into browse mode becomes the default tab when you move to that layout.

I have not tested this extensively but it appears to be the case. Has anyone noticed anything different?

You can set the default by double clicking on the tab in layout mode. It puts a black border around it.

That is not the problem. What i really need is a go to tab script step or Get(ActiveTab) which I realize is not in filemaker. Duh.

I figured out a solution - just create two different fields, put one on each tab. Then from each tab, run the script with a different script parameter and use a go to field based on that parameter. works good although I am disappointed that this functionality is not built in to tab controls.

You can set the default by double clicking on the tab in layout mode. It puts a black border around it.

I don't see that behaviour in the windows version. The tab that is showing when you exit layout mode whether it is selected by double-clicking or single-clicking becomes the default. However, as you say, this is not relevant to your question and the solution you have selected seems to be the common way of dealing with movement amongst tabs. I agree that selecting a tab should be scriptable. Putting a tab control on a layout hides part of the layout and this needs to be made accessible without user intervention or work-round tricks. No doubt it will give us a reason for buying version 9.

Perhaps I should put this in a different forum, but: I've just realized that the "go to field" workaround to effect a "go to tab" behavior does NOT work in Instant Web Publishing. Having been so happy to discover that trick myself (before coming here), I forgot to test it in WebView until I was already counting on it! (oops)

:)