Keydown and SendKeys

[Remster]

Hi Folks

I have a control, which I'll call 'MyField', on a form. I also have code for the control, which I'll simplify to this:

 
Private Sub MyField_GotFocus()
 
    SendKeys "{F2}"
 
End Sub

 
Private Sub MyField_KeyDown(KeyCode As Integer, Shift As Integer)
 
    If Not (KeyCode = vbKeyF2 Or KeyCode = vbKeyTab) Then MsgBox "You can't do that." 
 
End Sub

What's puzzling me is this: when MyField receives the focus by tabbing, the message box appears. So the SendKeys command is triggering the KeyDown event, as required, but there's no recognition that the key in question is F2 (or Tab). What am I doing wrong?

Thanks

Remster

[boblarson]

Why are you using SendKeys and F2? Are you wanting to select the entire field? That's what I seem to get when entering a control and hitting F2. So you can do that with code by using:

Me.TextBoxNameHere.SelStart = 0
Me.TextBoxNameHere.SelLength = Len(Me.TextBoxNamehere)

[Remster]

Yes, that's exactly what I want to do (select the entire field on entry), so I'll try your suggestion later. Thanks.

Here's a very closely related case that I'm struggling with:

 
Private Sub OptionButton_KeyDown(KeyCode As Integer, Shift As Integer)
 
    If KeyCode = vbKeyRight Then
        SendKeys "{TAB}"
        DoCmd.CancelEvent
    End If
 
    If Not (KeyCode = vbKeyRight Or KeyCode = vbKeyTab) Then MsgBox "You can't do that." 
 
End Sub

What I'm trying to achieve here is to make the cursor keys move to the next field rather than scroll through the options. I can't (or at least don't want to) use SetFocus, because the next enabled field will vary depending on a range of conditions. Is there a way to say something like 'move to the next enabled field'?

If I can solve this, I shan't need to worry about the SendKeys issue.

[ajetrumpet]

What I'm trying to achieve here is to make the cursor keys move to the next field rather than scroll through the options.

I don't get that. Cursor keys? Scroll through the options? What does this stuff mean??

I can't (or at least don't want to) use SetFocus, because the next enabled field will vary depending on a range of conditions. Is there a way to say something like 'move to the next enabled field'?

Of course there is, change the keycode to TAB, which is 9. so in your code, if you want to move to the next enabled field if the user presses Right arrow or tab, maybe write:

Private Sub OptionButton_KeyDown(KeyCode As Integer, Shift As Integer)
 
    If KeyCode = 27 or KeyCode = 9 Then
        KeyCode = 9
    else 
        MsgBox "You can't do that." 
    end if

End Sub

what does docmd.cancelEvent do? Never used it.

[Remster]

I don't get that. Cursor keys? Scroll through the options? What does this stuff mean??

Sorry, perhaps that was too British and too elliptical.

Cursor keys = arrow keys

Scroll through the options = move the focus from the first option to the second, then the third, then the fourth, then back to the first, and so on

Perhaps this would have been clearer: 'What I'm trying to achieve here is to make the arrow keys move the focus to the next control rather than to the next option button in the option group.'

Of course there is, change the keycode to TAB, which is 9. so in your code, if you want to move to the next enabled field if the user presses Right arrow or tab, maybe write:

Private Sub OptionButton_KeyDown(KeyCode As Integer, Shift As Integer)
 
If KeyCode = 27 or KeyCode = 9 Then
KeyCode = 9
else 
MsgBox "You can't do that." 
end if
 
End Sub

Thanks, I'll give that a try.

what does docmd.cancelEvent do? Never used it.

I think (it's several months since I wrote that code) it cancels the normal behaviour of the arrow key. So if I have just ...

 
If KeyCode = vbKeyRight Then
    SendKeys "{TAB}"
End If

... I get the normal arrow key behaviour plus the tab key behaviour. But if I have ...

 
If KeyCode = vbKeyRight Then
    SendKeys "{TAB}"
    DoCmd.CancelEvent
End If

... I get just the tab key behaviour. I hope this isn't Martian.

[Remster]

Okay, this works:

If KeyCode = vbKeyRight Or KeyCode = vbKeyDown Then KeyCode = vbKeyTab

Now what I need to know is how to simulate Shift+Tab for the other two arrow keys:

If KeyCode = vbKeyLeft Or KeyCode = vbKeyUp Then KeyCode = vbKeyTab ... ?

Any ideas? I've tried a variety of things, none of which has worked.

[ajetrumpet]

[/INDENT]Now what I need to know is how to simulate Shift+Tab for the other two arrow keys:

If KeyCode = vbKeyLeft Or KeyCode = vbKeyUp Then KeyCode = vbKeyTab ... ?

Any ideas? I've tried a variety of things, none of which has worked.

for that you'll have to use sendkeys, and change the keycode to 0. using shift with other keys is in the sendkeys helpfile.

[Remster]

Damn, then it's back to Square One (see my original post). Thanks for your help though.

[boblarson]

for that you'll have to use sendkeys, and change the keycode to 0. using shift with other keys is in the sendkeys helpfile.

Wrong. You don't need SendKeys. You can do it like this:

Private Sub Form_KeyDown(KeyCode As Integer, Shift As Integer)
    Dim intTI  As Integer
    Dim ctl    As Control
    On Error GoTo Errors
    If KeyCode = vbKeyRight Then
        intTI = Me.Controls(Me.ActiveControl.Name).TabIndex + 1
        For Each ctl In Me.Controls
            '            On Error Resume Next
            If ctl.TabIndex = intTI Then
                ctl.SetFocus
                ctl.SelStart = 0
                ctl.SelLength = Len(ctl.Text)
            End If
GTNext:
            
        Next
    End If
    KeyCode = 0

ExitHere:
    Exit Sub
Errors:
    Select Case Err.Number
        Case 438, 3270
            Resume GTNext
        Case Else
            MsgBox "Error " & Err.Number & " - " & " (" & Err.Description & ") in procedure Form_KeyDown"
    End Select
    Resume ExitHere
    Resume
End Sub

[Remster]

Thanks. I'll give that a try and let you know if I can get it to work.

[boblarson]

Thanks. I'll give that a try and let you know if I can get it to work.

Make sure that the FORM'S Key Preview property is set to YES as well.