Tab Control Tabs

[AEROTJK]

When building a tab control, is there an option to have the tabs on the
bottom, sides of the control instead of the only the top?

 

[Douglas J. Steele]

No, there isn't. (At least, not with the tab control built into Access.
There may be 3rd party tab controls you could buy to use instead)

 

[Linq Adams via AccessMonster.com]

A workaround would be, in Design View, to design each page like you want it
to look. You need to do this, because after the next step, the tabs disappear
in Design View as well as when the form is run, and changing them in Design
View is impossible. If you make a mistake, you can always change the Style
back to Tabs temporarily.

Next, select the tabbed control (the entire control, not one of the tabbed
pages) and goto Properties - Format and set the Style Property to "None."

Next, create your own command buttons, placed wherever you want them.

In code behind the command buttons, use code like this

Private Sub Page1_Click()
Me.YourTabControlName = 0
End Sub

Private Sub Page2_Click()
Me.YourTabControlName = 1
End Sub

and so forth. Notice that the Values for pages is Zero-based, so for Page1
you use 0, for Page2 you use 1, etc.

 

[David W. Fenton]

A workaround would be, in Design View, to design each page like
you want it to look. You need to do this, because after the next
step, the tabs disappear in Design View as well as when the form
is run, and changing them in Design View is impossible. If you
make a mistake, you can always change the Style back to Tabs
temporarily.

Next, select the tabbed control (the entire control, not one of
the tabbed pages) and goto Properties - Format and set the Style
Property to "None."

Next, create your own command buttons, placed wherever you want
them.

In code behind the command buttons, use code like this

Private Sub Page1_Click()
Me.YourTabControlName = 0
End Sub

Private Sub Page2_Click()
Me.YourTabControlName = 1
End Sub

and so forth. Notice that the Values for pages is Zero-based, so
for Page1 you use 0, for Page2 you use 1, etc.

Actually, an option group with toggle buttons is a better choice
than individual command buttons, and then you can assign the tab
values to the options, and in the AfterUpdate use:

Me!ctlTab = me!optTab

I've done this many times.