To click - or not to click...

[David618]

New question. On my Log In form, there's a command button (cmdLogin) that runs code on click, but I would also like that same code to run if the user also depresses "enter." I typically enter values and hit "enter" instead of reaching for the mouse and clicking on the command buttons, so I would like for users of my app to have the same convenience. Thoughts on how to do this?

[June7]

That would require code that checks if the Enter key was pressed - this is the Key Press event of the form or data controls.

Alternatively, if you only want code to run if data is entered/edited, use the AfterUpdate event.

[Beetle]

I don't believe the KeyPress event recognizes the Enter key. I would use the KeyDown event. Example;

Private Sub YourTextBox_KeyDown(KeyCode As Integer, Shift As Integer)
    If KeyCode = vbKeyReturn Then
        Call cmdYourButton_Click
    End If
End Sub

[David618]

What would be the code that checks if the Enter key was pressed? I see the Key Press event on the property sheet for the command button (cmdLogin - labeled "Enter"). Would it be the same code for "Private Sub cmdLogin_KeyPress(KeyAscii As Integer)" as "Private Sub cmdLogin_Click()"?

[David618]

I think I understand. It would be:

Private Sub cmdLogin_KeyDown(KeyCode As Integer, Shift As Integer)
    If KeyCode = vbKeyReturn Then
        Call cmdLogin_Click
    End If
End Sub

[Beetle]

No. You wouldn't trap it in the command button, you would trap it in the last text box where you enter a value just before you would normally click the command button.

[DepricatedZero]

The Enter key is problematic, because Access has it reserved for switching between fields. At least in 2007. Not sure if there's a way around that, I never found one. My login form just has an AfterUpdate event fire on the password. Enter causes it to leave the field, which fires the AfterUpdate, or if they click the Login button it also fires - no one has ever noticed the difference, and I'll be making it proper once I convert it to VB.NET

[Missinglinq]

Just use the Default Property of the button: In Form Design View, with the cmdLogin selected, go to Properties - Other and set the Default Property to Yes. When <Enter> is pressed the cmdLogin code will fire.

Linq ;0)>

[June7]

Linq, I see that behavior even if the property is set to No. Of course, the button must have focus so I just tested with Default set as Yes and the button Click event fires regardless of where the focus is. Don't like that.

[Missinglinq]

...the button Click event fires regardless of where the focus is. Don't like that...

Be that as it may, it is the behavior the OP asked for! I wouldn't use it on most Forms, but on a login Form, with a user control, a password control and a submit button, it's not apt to cause problems.

Linq ;0)>