command buttons for tab pages

[Imran Ghani]

Hi! I have build my application with tab pages. I want to apply command
buttons at the bottom of the tab pages and I want to use these set of command
buttons to perform their related tasks on all the tab pages, I mean whichever
page is the current page. I am a novice and I looked for something like
footer at the bottom of the tab pages but could not find. Kindly guide me, do
I have to make a set each for every tab page, or can I just create one set of
command buttons at the bottom which could perform functions on all the tab
pages. Thanks in advance.

 

[Jack Leach]

You can use one set of buttons to handle all of the tab pages, although these
buttons would ideally be somewhere other than on the tabs themselves (I would
keep them in the detail but just under or above the tab control). If you
want these on the tab pages themselves you will need a set for each tab.

A tab control does not act like a subform, in the sense that all
controls/tabs etc can be referred to just as if it were not on a tab page
(there is no special "callout" for controls on tab pages like there is on
subforms).

That said, you can refer to the tab control from the code of your buttons to
navigate from one tab to the next. The trouble that you are going to run
into as that the index value and physical order of the tabs may not be the
same. Selecting a tab by it's index is easy enough, but you may have to
refer to the "name" property of the tab page to select it.

I'm not familiar with the exact syntax off the top of my head and don't have
the resources to check it at the moment, but the above is what you can
expect. Me.tabcontrolname. should bring up a list of properties and methods
you can utilize to work with this.

hth
--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)

 

[Jack Leach]

You can use one set of buttons to handle all of the tab pages, although these
buttons would ideally be somewhere other than on the tabs themselves (I would
keep them in the detail but just under or above the tab control). If you
want these on the tab pages themselves you will need a set for each tab.

A tab control does not act like a subform, in the sense that all
controls/tabs etc can be referred to just as if it were not on a tab page
(there is no special "callout" for controls on tab pages like there is on
subforms).

That said, you can refer to the tab control from the code of your buttons to
navigate from one tab to the next. The trouble that you are going to run
into as that the index value and physical order of the tabs may not be the
same. Selecting a tab by it's index is easy enough, but you may have to
refer to the "name" property of the tab page to select it.

I'm not familiar with the exact syntax off the top of my head and don't have
the resources to check it at the moment, but the above is what you can
expect. Me.tabcontrolname. should bring up a list of properties and methods
you can utilize to work with this.

hth
--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)

 

[John W. Vinson]

You can use one set of buttons to handle all of the tab pages, although these
buttons would ideally be somewhere other than on the tabs themselves (I would
keep them in the detail but just under or above the tab control).

Actually you can create the buttons elsewhere on the form and drag them "in
front of" the tab control. They'll logically be on the form itself, not on any
tab page, and will be visible on all the pages (because they're not actually
ON the page).

 

[John W. Vinson]

You can use one set of buttons to handle all of the tab pages, although these
buttons would ideally be somewhere other than on the tabs themselves (I would
keep them in the detail but just under or above the tab control).

Actually you can create the buttons elsewhere on the form and drag them "in
front of" the tab control. They'll logically be on the form itself, not on any
tab page, and will be visible on all the pages (because they're not actually
ON the page).