I have a big layout with 8 tabs and some of the tabs hold another 6 tabs. Should I split them (the first 8 tabs) into single layout to speed up things in Web Direct? Or this is already optimized by FMS?
Your point of view.
You may want to explain a little bit more about your solution and post your TO Graph so users have a better idea of what your database does. Version? Platform Used?
It's just a plain layout with a lot of fields in it, separated within TAB in two level. Is it better to separate the TABS in several layout to speed up thing (less fields to load) or FMS is already loading only fields and stuff that are in the current showed TAB?
High Sierra 10.13.6
I can't really comment about performance issues, but as a general rule I avoid using tabs these days. I find them a bit ugly looking. Where I need to layer things I find the slide control much cleaner, smarter looking device, but I also nowadays avoid the multi-layered layout because it so much messier from a development perspective—all those fields on a single layout can become quite a maze. Nowadays, as a rule I prefer layouts fit for purpose, so I would lean towards a layout for each tab set. When tab controls were introduced they were pretty much the only device that gave you more screen real estate, but now there are several options if this is what you need—popovers, slide controls in particular.
echo: I also use button bars in combo with slide panels (much more flexible/variable).
What I consider: is the layout so complex, that it's difficult to revise/report/enter data? Then I rethink my design.
With the Card Window, so of this is much more elegant (don't leave a record) to provide the 'other tabs' of data. This is also more flexible to revise and report!
Retrieving data ...