Tabstrip tab stop behaviour...

[Guest]

Hello!

I have a four page tab strip ('tab control' on tool box) in the middle of a
form. The tabs are hidden (style = None), and each of the four pages contains
a few bound text or combo controls that the user must fill in. Progression
through each page is controled by back and next buttons that make up a wizard
to complete this bit of the form. There are other bound text box fields on
the main form before and after the tab strip area.

My problem is in setting the tab stop behaviour. I want the user to be able
to tab through the text boxes from the top of the form, and seemlessly tab to
the first text box on page one of the tabstrip. Unfortunately, even though
the tabs on the tabstrip are hidden, they still act as a tab-stop. this means
that the user has to press tab twice to get to the first text box on the
tabstrip.

If I set the 'Tab Stop' property of the tabstrip to No then the controls of
the tabstrip page are missed entirely (as expected). Any ideas?

(Access 2003 SP3, Win XP)

Cheers,
Dave

 

[Rick Brandt]

Hello!

I have a four page tab strip ('tab control' on tool box) [snip]
My problem is in setting the tab stop behaviour. I want the user to
be able to tab through the text boxes from the top of the form, and
seemlessly tab to the first text box on page one of the tabstrip.

[snip]

Best solution (IMO) is to place a tiny (but Visible = Yes) TextBox on each page
and make it last in the TabOrder on that page. In the GotFocus event of that
TextBox run a line of code that sets focus to the desired control on another
page. This way when the user tabs out of the last "real" control on your page
they will automatically be taken to the desired control on the other page, but
if they move off of that last real control with the mouse or by using
<shift-tab> then the form will still take them where they expected to go.

 

[Guest]

Best solution (IMO) is to place a tiny (but Visible = Yes) TextBox on each
page

and make it last in the TabOrder on that page. In the GotFocus event of that
TextBox run a line of code that sets focus to the desired control on another
page.

Genius! Works perfectly, thanks Rick!