KeyAscii won't capture the <Tab> key

[Guest]

Hi;

In my procedure below, I need to capture the <LineFeed > <Space> <Tab> or
<Click>. I have managed to redirect everything but the <Tab>. I have tried
various values including 9, "9", Chr(9) and vbTab. Nothing works.

What can I do to make <Tab> execute the right procedures rather than jump to
the first enabled control? Something in Excel is overriding VBA.

Private Sub EnterButt0_KeyPress(ByVal KeyAscii As MSForms.ReturnInteger)


If KeyAscii = 9 Then
InsertBlankRow
CntrlsOpen
DayJoinedTxt0.SetFocus
End If

End Sub

Regards Bill

 

[Bob Phillips]

If this is a userform, why not just trap the exit event?

--
HTH

Bob Phillips

(replace somewhere in email address with gmail if mailing direct)

 

[Peter T]

Hi Bill,

From help -
"The KeyPress event occurs when the user presses a key that produces a
typeable character (an ANSI key) on a running form while the form or a
control on it has the focus."

Keypress will not return Tab, Enter or Arrow keys

Use either the Keydown or KeyUp events and return Keycode.

What can I do to make <Tab> execute the right procedures rather than jump to
the first enabled control?

I'm not sure what you mean by "execute the right procedures" but maybe
merely changing the tab orders (Tabindex) will suffice, try the tab wizard
in View > Tab order.

Regards,
Peter T

 

[Guest]

Hi Peter;

Thanks; KeyDown solved it. What is the difference between KeyDown and Keyup
? I know how keyboards work; i.e. scan codes and all that; but
programmaticlly why might I choose KeyDown over KeyUp or viceversa in VBA?

By "execute the right procedures" I meant the two procedures, "InsertBlankRow
CntrlsOpen", that I had included with my original sample.

Regards Bill

 

[Peter T]

What is the difference between KeyDown and Keyup

The KeyDown occurs when you hit a key with the control in focus and Keyup
when the key is released. If the key is a tab or arrow key (or alt shortcut)
you might only get keydown of the original control and keyup of the newly
activated control. I'm thinking this answer seems too obvious or did you
mean something else!

Regards,
Peter T

 

[Guest]

Hi Peter;

Your right, that was obvious. I was trying to avoid that answer when I
wrote "but
programmaticlly why might I choose KeyDown over KeyUp or viceversa in VBA? ".

What I meant was: when I come to write code for a key action the VBE gives
me a choice of "Private Sub ButOrWhatever_KeyDown(ByVal KeyCode As
MSForms.ReturnInteger, ByVal Shift As Integer)" and "Private Sub
ButOrWhatever_KeyUp(ByVal KeyCode As MSForms.ReturnInteger, ByVal Shift As
Integer)". For most uses it seems that it will do the same thing as far as a
User is concerned. When I am writing the code to be executed for a key
action, is there any inherent advantage of choosing keydown over keyup.

Nothing I have read indicates any programming advantage of 'up' over 'down'.
But then, nothing I read or googled for told me that 'KeyPress' couldn't
trap <Tab>.

So I guess I was asking if there was some poorly docummented programming
difference other than the obvious Keyboard scanning or looping or mechanical
difference.?

Regards Bill

 

[Peter T]

I wouldn't say there's any particular advantage over keydown vs keyup, it's
case of which event best suits needs. Eg do you want to react the moment
user presses a key or when it's released, In some scenarios you might want
to trap both events. The keycode will return same in both events.

I've never found a use for the Keypress event in VBA, though I suppose it
might be useful to return the 'character' code, ie keyascii, rather than
keycode which is not necessarily the same, eg "a" or "A", or directly return
characters that have dual keys such as numbers.

Regards,
Peter T