ralph
8/25/2010 11:59:00 AM
On Wed, 25 Aug 2010 06:51:34 -0400, Nando
<hightech@att.net.no.to.sp.am> wrote:
>I have been using SSTab for as long as I can remember (in both VB6 and
>VBA6). Just wondering if there are other reasons why I should consider
>using MSCOMCTL's TabStrip instead.
>
>TabStrip Control
>Microsoft Windows Common Controls 6.0 (SP6)
>MSCOMCTL.OCX
>
>SSTab Control
>Microsoft Tabbed Dialog Control 6.0 (SP5)
>TABCTL32.OCX
>
>TabStrip requires the developer to create and manage the control
>containers for each page. While the SSTab control is friendlier (each
>tab is already a control container).
Your last comment sums the basic difference.
The SSTab is a container (or a Control with multiple containers), the
TabStrip is not. The SSTab contains all the controls, while a TabStrip
control acts like a controller or manager. Thus the SSTab has a larger
amount of overhead. Not too noticeable if you are using only one, but
if you have several forms with the SSTab your executable is much
larger.
Other minor differences:
1) You can skip having to distribute another OCX.
2) The SSTab hides and shows its containers by drawing off or on the
current window. With the TabStrip you have to manage 'visibility'
yourself (or of course do the same thing). This can be consider either
extra control, or no control depending on view or needs.
3) This can cause other problems if you are trying to dynamically add
or move 'contained' controls within a SSTab as the Top and Left
positions of non-visible controls are essentially "non-valid".
I'm sure others will be along with more.
IMHO, the SSTab is obviously easier to develop with, but in the long
run the greater control and lighter weight of the TabStrip make it a
better choice.
-ralph