I want to run scripts when I move between tab panels on a layout (including sub-tab panels).

What the simplest way of doing this? When adding buttons over the tab header FP acts as though they are not being seen.

This seems like an innocent question, and there is a workaround:

http://www.fmforums.com/forum/showpost.php?post/225429/

...but it's unfortunately more likely a inadequate relational structure underneath, which bothers:

http://www.fmforums.com/forum/showtopic.php?tid/191906/post/275200/hl//fromsearch/1/#275200

But could also be a misjudgement of the tool at hand:

http://www.fmforums.com/forum/showpost.php?post/256765/

--sd

Hi Soren

Thanks for your swift reply and the links.

To give you more insight, I'm trying to build a product and product attribute system for products that will (or may) have an unlimited number of product attributes which will eventually be used to replace a traditional hierarchichal category system.

My aim is to design the product interface so that the user can go to a specific tab and select attributes from a portal on the tab panel to create product attributes. The portal shown would be the records in the attributes table based on the attribute group ID of the attributes and therefore I was planning, when moving between the tab panels, to set the attribute group ID to a global field to establish the relationship for the portal. (I think very similar to your Leases file concept, but with tab panels)

I guess I could create a number of global fields per attribute groups that I want to present - and create the relationships as well - and then show different portals, but I was hoping to keep this as clean as possible by just using the one global field.

Which brings me back to the tab script issue. In this case is Option 1 my only option?

have an unlimited number of product attributes which will eventually be used to replace a traditional hierarchichal category system.

Interesting, do you by it, rule out recursive structures?? Another matter I came to think of is:

http://www.filemakermagazine.com/videos/data-tagging-classification-vs-organization.html

--sd

I don't understand why you need the tab panels or several global fields. Couldn't this be ONE portal, filtered by ONE global field? You could select the group to view by changing the global field's value to the desired AttributeGroupID. The field could be a drop-down menu or - if you wish - you could have buttons looking like tabs, with each button switching the global to a different group.

I would like to know what should be written on the different panes, perhaps it gives a better idea as to what's wished to be achieved!

--sd