A tabstrip control resembles a card index file that contains various screens belonging to a single application. Tabstrip controls allow you to insert several components of an application on a single screen and to navigate between them.
You use tabstrip controls to give complex applications a uniform structure and to make it easier for users to navigate between their components.
We recommend you use tabstrip controls when a single object or application has different components or logical views. Property sheets are typically used to enter the attributes of complex objects.
The components of a tabstrip control are described in the figure below.
Tab titles contain the titles of the components to which the user can navigate. You can add icons and text to the tab title in the same way as for pushbuttons.
The first row of the tabstrip control is reserved for tab titles. If you have defined more tab titles than can be displayed at one time, the system automatically displays scroll buttons in the top right-hand corner of the tabstrip control to enable you to scroll between the tab titles.
A tab page contains a group of fields that logically belong together. Tab pages are implemented by means of subscreens.
The screen environment around the tabstrip must remain constant. When you switch between tab pages, menus, application toolbar, and other fields, the tabstrip control must not change.