sorry forgot to attach screen shots
There are several options and Whether or not you are using FileMaker 12 or newer can make some of those options easier to implement than if you are using an older version.
The simplest option is to use Two layouts, your original layout and one modified for "knitwear". Scripts, which can be performed by script triggers such as OnRecordLoad can switch layouts as needed so that you see the correct layout for the current record.
But more sophisticated options are also possible where you might place an invisible tab control inside a given tab panel. Selecting a tab of the current tab control can trip a script trigger for a scrip that then uses Go to Object to select the correct tab panel (or slider panel) of the invisible tab control.
There's a key difference to keep in mind: With two separate layouts, you can base them on different table occurrences and thus refer to data in related tables from different starting points in your relationship graph. If you keep it all in one layout, on the other hand, you must set everything up to work from the same starting point.
Im using Filemaker 12 pro advanced.
I have a bit of a hard time to visualize the two key differences. Whats the disadvantages of keeping everything in one layout and setting everything up from same starting point..?
If I fx just want to have a radio controlling if it's knit or woven (and controlling what layout are in the other tabs) I would have for go for a more sophisticated solution..?
It might help to read this thread on the Anchor Buoy method or organizing groups of table occurrences within your database: http://sixfriedrice.com/wp/six-fried-rice-methodology-part-2-anchor-buoy-and-data-structures/
Each layout is based on a specific table occurrence. If you use two layouts for this, each layout can be based on a different table occurrence and data from related tables for portals and such can be controlled by a different set of relationships.
For some data models, that may make it much easier to set up and work with your two different sets of data for your two basic categories (KnitWear and NonKnitWear).
It also can make for simpler layouts where the features of the layout are easier to see and work with in Layout mode as you aren't dealing with invisible objects.
On the other hand, two layouts means that you may find yourself having to painstakingly make identical changes to two layouts in order to maintain the illusion that there is only one layout where one or more of the tabs in the tab control magically change when a Knitwear record is brought up on the screen.
Please note that I am not recommending one option over the other.
Think I'll better stick to two layouts sounds a lot easier, and less complicated. Is there anywhere I can read or see a tutorial about how to approach this problem..?
I don't know that you really need a tutorial. Go to the layout, enter layout mode and select "Duplicate Layout" from the Layout menu. You now have two identical copies of the same layout. Edit one of the two copies to become what you want for "Knitwear".
Then see if you can set up OnRecordLoad in LayoutSetup on both layouts to perform a script that changes layouts as needed to use the correct layout for each type of record.
I put in a set of Radio Buttons which I called 'Type switch' to determine whether a record should show the 'woven' Layout or the 'knit' layout.
An then I attached the underneath script to an OnRecordLoad in the layout setup, which kind of works. Is it possible to have this also work when I switch when I change the radio button..?
If [ TECHNICAL SHEET 2::Type switch = "Woven" ]
Go to Layout [ “TECHNICAL Spec Woven” (TECHNICAL SHEET 2) ]
Else If [ TECHNICAL SHEET 2::Type switch = "Knit" ]
Go to Layout [ “TECHNICAL Spec Knit” (TECHNICAL SHEET 2) ]
You can use the OnObjectModify trigger on the radio button field to perform the same script.
sorry wasn't thinking, thank you so much for your help again...