Tab from Form Detail to Form Footer

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I have a simple form to change a password, asking the user for current
password, new password, and confirm new password, in the form detail section.

In the form footer section, I have an OK and CANCEL button.

When the user tabs from the confirm password text box, I'd like the cursor
to tab to the footer section, specifically to the OK button.

I guess I could put code in the ON EXIT event, but how would I account for a
reverse tab (SHIFT-TAB) as opposed to just the TAB key?

Any ideas how to do this?

Thanks,
 
if the form is unbound, and is in SingleForm view, then the easiest solution
is simply to move the command buttons into the Detail section; there's no
need to have them in the Footer section under the above stated conditions.

hth
 
I could do that Tina, but I have them there to support a coloring scheme we
use in the header and footer background color.
 
David said:
I have a simple form to change a password, asking the user for current
password, new password, and confirm new password, in the form detail section.

In the form footer section, I have an OK and CANCEL button.

When the user tabs from the confirm password text box, I'd like the cursor
to tab to the footer section, specifically to the OK button.

I guess I could put code in the ON EXIT event, but how would I account for a
reverse tab (SHIFT-TAB) as opposed to just the TAB key?


How about using the confirm text box's AfterUpdate event to
set the focus to a the button in the footer?
 
if you're setting the Footer section to a specific color, you can just add a
rectangle control to the Detail section, as wide as the section and as high
as you need it to be, set it's Border to transparent, and it's color to the
color you need. move it "behind" the command buttons so it doesn't cover
them up.

hth
 
Tina,

Thanks for replying.

I thought of that, but will that box stretch to size if they maximize the
form?
 
Marshall,

Could do that code in the AfterUpdate vs. the OnExit event where it is now.

But, how will that account for a SHIFT-TAB keystroke (how to I evaluate
whether they hit SHIFT-TAB vs. just TAB?

Thanks.
 
David said:
Could do that code in the AfterUpdate vs. the OnExit event where it is now.

But, how will that account for a SHIFT-TAB keystroke (how to I evaluate
whether they hit SHIFT-TAB vs. just TAB?


What does it matter if the value is not changed?

The trouble with the Exit event is that it runs even when
users are just navigating around the form. It seems to me
that you only care about it when they actually enter
something.
 
Thanks Marshall.

Just determined the "other" reason this does not work: If the user clicks
on the OK button vs. tabbing to it, it requires two clicks of the OK button:
First click moves the focus to the OK button, per the AfterUpdate routine,
the 2nd click of the OK button does the OnClick event.
 
David said:
Just determined the "other" reason this does not work: If the user clicks
on the OK button vs. tabbing to it, it requires two clicks of the OK button:
First click moves the focus to the OK button, per the AfterUpdate routine,
the 2nd click of the OK button does the OnClick event.


Sounds like a Catch22. I don't see how you can have it both
ways.
 
Back
Top