How does one code the tab strip control events and make them fire

[Guest]

In other words, I'm attempting to code the control's Update event so that
another control such as a textbox or lable will either display/ not display.
However, I'm limited to using the Tabstrip control that comes standard with
Access 2003 upgrade. It seems that nothing I code fires. I also note that any
controls that I place on the tab strip control's canvas will not display when
I launch the form containing the tab strip control. What's this all about?

I've tried setting the visible property to true, setting the format/ align
to set the tab strip control to back and the label control to "bring to
front." Nothing works!

 

[david epsom dot com dot au]

I don't know why your events aren't working, but
the reason you can't see your other controls is
because you have placed them on the form, underneath
the tab control. Try cutting them out and placing
them again.

(david)

 

[Guest]

David,

I've tried placing a label on the form first, and then placing it on top of
the tabstrip. It doesn't even display under those conditions. I've explicitly
set format on the menu bar to bring the label control to front and send the
tabstrip control to back.

Another strange thing is where I could place a subform on top of the
tabstrip, and it displays. However, when I try to reference the subform to
change a property based on which tab is clicked on, Access doesn't recognize
the subform at all.

I've also made sure to include appropriate lib files in the refernces while
in the VB Editor mode. So, I'm at a loss right now.

 

[Brendan Reynolds]

Are you *sure* you're using the built-in tab control? The reason I ask, is
that you refer to an 'Update' event, and the built-in tab control does not
have an Update event. But perhaps you meant the Update event of one of the
controls you are placing on the tab control?

If you are using the built-in tab control, you may find the article at the
following URL helpful ...

http://office.microsoft.com/en-us/assistance/HA012300491033.aspx

 

[Guest]

Brendan,

thank you very much. You referred me to exactly what I needed. I also
discovered that I do in fact have the appropriate Tab control. When you
pointed out to me that this control was available from the toolbox, that made
me aware that I wasn't seeing it in my Access application when I displayed a
form in design view. I figured out what to do from there to get the full
listing of standard controls to display in the toolbox.

So, I'm good to go. Access 2003, at least what I have encountered, has some
strange functionality at times.

 

[Brendan Reynolds]

Does this mean that you are actually using an ActiveX tab strip control,
rather than the native Access tab control (which is on the toolbox by
default)? If it does - well, if the ActiveX control meets your needs, and if
you are developing an app for your own use, on your own PC, great. If you
are planning to distribute the app to others, though, using external ActiveX
controls like this can make deploying the app more complicated.

 

[Guest]

No, I am using the standard control. It just wasn't showing up in the group
of controls for some reason until I actually invoked form header/ footer to
display on the form in design view. Then I had access to it. Otherwise, yes,
I was attempting to use an ActiveX control from the controls available via
registered OCX's. But, since I'm working for a major company that does a lot
of outsourcing, it's not always a simple matter to get licensing of DLL's or
OCX's, which obviously what prevented my being able to use one of those
controls rather than the standard tab control that ships with Access and is
distributable as you pointed out.

 

[Guest]

set format on the menu bar to bring the label control to front and send
the

tabstrip control to back.

You haven't got it right yet. The label control has to be "inside"
the tab page, not in front or behind.

However, when I try to reference the subform to

Remember that there is both a subform control, and a form
inside the control. If you have a control and a form with
the same names, change the control name to make things
clearer. The control will have the control properties, including
".Form" which is the property referring to the child form.

(david)