Conventional Tab Control Use.

[ApexData]

I'm getting the impression that TabControls are used predominately for
paging through a large number of fields that normally would not fit on
a single form and that to use it otherwise (ie Opening related tables)
is unconventional.

I like the asthetic effect the Tabs offer, and I've used it as a Menu
for users to tab to different forms, rather than have the form being
launched by a button. In a Personnel system I'm building, the first 2-
tabs display fields from the Maintable. The other fields open tables
linked to the main table. One tab opens a continuous subform that
shows the current Employees promotion history. Another tab similarly
shows the current Employees Credentials,
etc...

Is this use of the TabControl accepted practice ???

Thanks
Greg

[storrboy]

On Feb 23, 4:53 pm, "[e-mail]" <[e-mail]:

I'm getting the impression that TabControls are used predominately for
paging through a large number of fields that normally would not fit on
a single form and that to use it otherwise (ie Opening related tables)
is unconventional.

I like the asthetic effect the Tabs offer, and I've used it as a Menu
for users to tab to different forms, rather than have the form being
launched by a button. In a Personnel system I'm building, the first 2-
tabs display fields from the Maintable. The other fields open tables
linked to the main table. One tab opens a continuous subform that
shows the current Employees promotion history. Another tab similarly
shows the current Employees Credentials,
etc...

Is this use of the TabControl accepted practice ???

Thanks
Greg

It is if it fits your needs and it works the way you intend it to. I
personally try to limit tab use to things like 'Options' forms or
other places where I don't have to be concerned about the way the user
navigates through it. If it makes sense to those who have to use and
maintain it, who's to argue?