Hack for scrolling through a tabbed form.

[Paul H]

I'd like Access to let me use Ctrl-PgUp and Ctrl-PgDn to scroll through a tab control on a form. I've looked through a variety of Keystroke combinations looking for Ascii codes, preferably Ctl-Page Up or Page Down, but no luck. Even if I did, I'm not sure where to put the event. I'd also like to put an event on the Esc key to close certain forms with a single keystroke. No luck there either.



This falls under the heading of idle curiosity, but if I knew how to do it, I would definitely put it to good use.

Thanks in advance.

Paul

[ssanfu]

I'd like Access to let me use Ctrl-PgUp and Ctrl-PgDn to scroll through a tab control on a form.

I'm not really sure I understand what you want to do. Do you mean you have, say, 10 tabs for a tab control and you want to use Ctrl-PgUp to move from Tab1 to Tab2??

In one dB I have, I am using the F12 key to open a more detailed form for a specific control. Then, in that form, pressing F12 in a specific control opens another more detailed form.... kind of drilling down 2 levels deep.

So I think it might be able to be done, I just don't understand what it is you are trying to do...

[Paul H]

All I am trying to do is navigate the tabbed form using the key board instead of the mouse. All that happens when I hit F12 is a Save As dialog box.

[ssanfu]

Didn't answer my questions....

All I am trying to do is navigate the tabbed form using the key board instead of the mouse.

Again......Do you mean you have, say, 10 tabs for a tab control and you want to use Ctrl-PgUp to move from Tab1 to Tab2??
You have not described the form design, nor posted an image of your form.

All that happens when I hit F12 is a Save As dialog box.

Again, I said "I am using the F12 key to open a more detailed form for a specific control". I programmed the F12 key to do something different than the default behavior. The first form has one behavior when F12 is pressed, the other form has a different behavior when the F12 key is pressed.


Maybe post your dB for analysis....

[Paul H]

Again......Do you mean you have, say, 10 tabs for a tab control and you want to use Ctrl-PgUp to move from Tab1 to Tab2??
You have not described the form design, nor posted an image of your form.

Yes, that is exactly what I am trying to do. I am a keyboard warrior. If I have my hands on the keyboard, I prefer to keep them there and use keyboard shortcuts and hot keys. I add my own where possible, I just haven't figured out this one.

Again, I said "I amusing the F12 key to open a more detailed form for a specific control". I programmed the F12 key to do something different than the default behavior. The first form has one behavior when F12 is pressed, the other form has a different behavior when the F12 key is pressed

I realized that after I posted my reply.

[Micron]

AFAIK
There are no keyboard events for a tab control page. It's the pages you want to navigate, not the tab control. Your post title is confusing as well. The form isn't tabbed - it contains a tab control. The control has pages. God only knows why it's not a page control, or has "tabs" if it's a tab control. It was bad enough; now there is a navigation control with tabs and a tabbed view for forms - with or without the tabs!!

AFAIK
There are no such keyboard events for a page that will work unless the page has controls that can take the focus. It will accept Tab key; I don't know what else.
I think you would have to
- have a control on a page that can take the focus and if e.g. key press is Tab key, get the active page property

Property Get ActivePage() As Access.Page
  With Me.TabCtl0
    Set ActivePage = .Pages(.Value)
  End With
End Property

- call the function in that keypress event and get the page name and Case Select to the next tab while dealing with which way to go when you get to the rightmost page. Then set focus to a control on the new page. It could be transparent, no border and maybe even zero width so that it's not obvious, but you will see the cursor flashing.

OR

You could use a mouse like the Almighty M$ planned.

[Paul H]

OR

You could use a mouse like the Almighty M$ planned.

[ssanfu]

If I understood you correctly, take a look at the example dB.

There is a tab control with 5 pages. The form, "Form1", is bound to Table1 just to have a couple of records.

As long as the form has focus, pressing {Alt+Page Up} or {Alt+Page down} moves through the tab control pages.

Took a while to modify my code to get it to work with the Page Up/Page Down keys.



Close???

[Paul H]

Looks very close. I've popped it in my form's keydown event, but I can't get it to fire. BTW, my form is structured just like yours, except my tab control is in the detail section. I don't know if that would make any difference. I have some other pressing matters which can't wait, but I'll return with my full reply asap, possibly Monday.

[Micron]

I can't get it to fire

Works for me.
EDIT - never mind. I see that you meant in your own code.

Don't understand why the tab control is in the footer though. Works even as a single form view with no controls and tab control in the detail section. The magic is in putting the event on the form, not the control or its pages.
It reminds me of why I keep hanging around here. Great place to learn stuff - especially tricks!

[ssanfu]

Looks very close. I've popped it in my form's keydown event, but I can't get it to fire. BTW,

Oops, I might have forgot to mention that the form "Key Preview" property must be set to TRUE. (Form Properties - Event tab - last property)
As I understand it, this allows the FORM to see the key strokes FIRST. If the code is not programmed to do anything with the key combination/code, then the control receives the key code(s).


As to why the tab control is in the form footer...... why not?
Actually, I tend to put sub forms in the form footer with both the main form and the sub form set to continuous form views. After setting the linking fields, Access complains and sets (Usually) the main form back to single form view. Then I set both forms back to continuous form views - life is good..
So, since it was an example form, I put the tab control into the footer just because.