MS Rant - TabIndexes

[Tony Toews [MVP]]

That's what I do. I turn off the tabs themselves using Style = None.
Although having no tabs makes it a little awkward to work on the tab pages
in design view, I can always switch from one tab page to another by
selecting the page in the object drop-down box or the property sheet.

Actually I'd put a line or two of code in the forms open event just to
change that setting automatically.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[Dirk Goldgar]

Actually I'd put a line or two of code in the forms open event just to
change that setting automatically.

Maybe, but I'm not sure if having space allocated for the tabs would affect
the desired layout of the form. I'll bear that in mind as something to try,
the next time I have occasion to build a "wizard" interface.

 

[Rick Brandt]

Maybe, but I'm not sure if having space allocated for the tabs would
affect
the desired layout of the form. I'll bear that in mind as something to
try, the next time I have occasion to build a "wizard" interface.

In that circumstance I just name the tab pages starting with "AAA" so that
they always appear at the top of the control list.

 

[David W. Fenton]

Maybe, but I'm not sure if having space allocated for the tabs
would affect the desired layout of the form. I'll bear that in
mind as something to try, the next time I have occasion to build a
"wizard" interface.

It does wreck the layout if you have the tab control very close to
the top of the detail area, or if the extra space the tabs take up
covers other controls.

I just use the dropdown, but, yes, it is something of a pain.

 

[David C. Holley]

But you could design the layout and shake down the functionality by placing
the controls in regions of a very enlarged form, thus avoiding the headache
of the overlap. If you go with a naming schema such as tb1_, tb2_ you can
then you code to move the controls into and out of position.

 

[raif]

I don't quite understand the problem here. Using the tab key skips
from page to page?

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[David W. Fenton]

But you could design the layout and shake down the functionality
by placing the controls in regions of a very enlarged form, thus
avoiding the headache of the overlap. If you go with a naming
schema such as tb1_, tb2_ you can then you code to move the
controls into and out of position.

I'd rather not code that. I certainly use naming conventions for my
tab pages (pge is my prefix for it), but don't see the point of
coding, as I don't know when the code should run. There's also the
new issue in A2002/2003 with runtime changes getting saved when they
oughtn't, which is a real thorn in my side in apps where I set
background colors and so forth at runtime.