Page tabs on a form

[Guest]

I hope this is a simple thing to fix. I have a form with two page tabs. When
people enter all the fields on tab 1, they are complaining about scrolling
all the way back up to click on the second tab to begin data entry on the
second page. I thought it would be nice to have a button they push at the
bottom to go to the next tab. From reading a couple other messages, it
sounds like the button they push would maybe change the focus to the first
field of tab two. Would this work?

 

[Van T. Dinh]

If you use a TabControl, you should design so that the Form ( & hence the
TabControl is fully visible on the screen if Access is maximized) so that
the users don't have to scroll the Form up & down. If you need more space,
simply use additional TabPage(s).

That's said, you can use a CommandButton to send the Focus to the "first"
Control (not "Field" - A Form has Controls and not Fields and Controls can
be bound to Fields in the RecordSource of the Form). Personally, I use a
dummy unbound TextBox (zero height & width, transparent background, no
border) as the "last" Control on the first TabPage and then use the GotFocus
Event to set the Focus to the "first" Control on the second TabPage. This
way, the user can tab out of the last Control visible to the user and he/
she gets to the "first" Control on the second TabPage.

 

[Al Camp]

bondtk,
You could create a button that executes a Domd.GoToControl "SomeField"
[SomeField] would be the name of the first control on Tab2.
You'll probably also need another button to also allow users to go to the
first control on Tab1.

But, I would recommend that you try your best to not design any form
that exceeds the length or width of your screen.
You've already seen that Scrolling is bothersome, as is PageUp and
PageDown
Add a third Tab if needed, or redesign your 2 tabs to try to get all
your data onto one screen. It's not a "serious" problem, but should
generally be avoided when at all possible.

 

[Guest]

Thanks for the good ideas! My first tab only slightly has to use the scroll
bar, but the people who are beta testing my design suggested the "next
button". I like the invisible field idea. I may switch from the button
approach to that approach.

bondtk,
You could create a button that executes a Domd.GoToControl "SomeField"
[SomeField] would be the name of the first control on Tab2.
You'll probably also need another button to also allow users to go to the
first control on Tab1.

But, I would recommend that you try your best to not design any form
that exceeds the length or width of your screen.
You've already seen that Scrolling is bothersome, as is PageUp and
PageDown
Add a third Tab if needed, or redesign your 2 tabs to try to get all
your data onto one screen. It's not a "serious" problem, but should
generally be avoided when at all possible.
--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions

I hope this is a simple thing to fix. I have a form with two page tabs.
When
people enter all the fields on tab 1, they are complaining about scrolling
all the way back up to click on the second tab to begin data entry on the
second page. I thought it would be nice to have a button they push at the
bottom to go to the next tab. From reading a couple other messages, it
sounds like the button they push would maybe change the focus to the first
field of tab two. Would this work?