Use of tab control: how is it? Stable?

[XP]

Using Office 2003 and Windows XP;

I am considering using a multi-ply tab control on a form; probably about
three to five tabs; I have read a lot on this forum and highly value your
input. I welcome comments from anyone, especially more experienced users and
MVPs.

1) Does anyone know of or had issues with this control? Is it stable to use;
does it run well/fast, etc.?

2) I'm presuming you can programmatically control it? i.e. Activate
different tabs, reference them from code and manipulate the controls on each
ply, etc.?

3) Any disadvantages to using the tab control?

Thanks much for any and all input.

 

[Albert D. Kallal]

One could argue that using lots of 3rd party activeX controls would reduce
stability in an access appcation.

However, for tab controls they are native to ms-access. I think I used them
in every application I written.

And, for those applications that did not have them...adding them did not
case any reduction in stability in anyway, shape or form..

So, they are no worse then using a combo box as far as I can tell. I don't
think ANY of the native controls cause a reduction in stability, the
excepting being the picture control.

1) Does anyone know of or had issues with this control? Is it stable to
use;
does it run well/fast, etc.?

It is very good. However, if you have 6 tabs, and behind each tab is a
sub-form, then you are loading up 6 sub-forms. However,
this would be no worse then a standard form with 6 sub-forms. In fact, what
you can do is leave the sub-form controls un-bound, and when you click on
the tab..you THEN set the sourceobject of the sub-form control the form you
want to display (hence, your tab control in this case is MUCH faster, since
you don't load any of the sub-forms until you actually need them. So, in
some cases, using a tab control, and moving sub-forms behind each tab
actually speeds things up..since you not loading ANY sub-forms until needed.

2) I'm presuming you can programmatically control it? i.e. Activate
different tabs, reference them from code and manipulate the controls on
each
ply, etc.?

Yes. Do note that any field on a form, or behind a tab control can still be
referenced as usually (there is not need to special code for referring a
control behind a tab...all controls are all available and don't need special
reference. If the fields+data behind each tab is to be a different form,
then you have to use a sub-form in those cases....

3) Any disadvantages to using the tab control?

Not much. The tab control is one of the MOST useful controls, and in user
interface studies, it comes out on top in terms of ease of use..and user
understanding. Hence, the tab contorl is a VERY good user control from a UI
friendly point of view when used correctly.

 

[Stefan Hoffmann]

hi,

1) Does anyone know of or had issues with this control?

No issues.

Is it stable to use; Yes.

does it run well/fast, etc.?

Compared with what?

2) I'm presuming you can programmatically control it? i.e. Activate
different tabs, reference them from code and manipulate the controls on each
ply, etc.? Yes.

3) Any disadvantages to using the tab control?

No.

Using subforms on the tab control may impact loading speed. This normal.
You can improve it by loading the subforms when switching the tabs.


mfG
--> stefan <--

 

[Marshall Barton]

Using Office 2003 and Windows XP;

I am considering using a multi-ply tab control on a form; probably about
three to five tabs; I have read a lot on this forum and highly value your
input. I welcome comments from anyone, especially more experienced users and
MVPs.

1) Does anyone know of or had issues with this control? Is it stable to use;
does it run well/fast, etc.?

2) I'm presuming you can programmatically control it? i.e. Activate
different tabs, reference them from code and manipulate the controls on each
ply, etc.?

3) Any disadvantages to using the tab control?

1) A couple of esoteric issues that most uses would never
see. The one I ran into was where the tab Style was set to
None and when tabbing into the tab control, the focus went
to an invisible something.

2) Certainly. To select a tab page in code, just set the
tab control's Value property. Use the Change event to
detect user tab selection.

3) Almost any alternative is going to require piles of
overlapping controls and a bunch of code to make them
visible/invisible according to some pseudo tab selection
mechanism. Use the tab control and only reconsider if you
run into a specific problem.

 

[XP]

Thank you all very much for your input; My comfort level just skyrocketed...

Thanks also for your time.

 

[Cheese_whiz]

I had this problem with a tab control once. It's nice to be aware of it's
potential so when you see it you'll know there's a way to fix it.

http://www.allenbrowne.com/ser-46.html

CW