EnterKey to press button in VBA Userform

calendar_today Asked Oct 1, 2013
thumb_up 6 upvotes
history Updated April 14, 2026

Direct Answer

You could also use the TextBox's On Key Press event handler: 'Keycode for "Enter" is 13 Private Sub TextBox1_KeyDown(KeyCode As Integer, Shift As Integer) If KeyCode = 13 Then…. This is a 7-line VBA Core snippet, ranked #81st of 95 by community upvote score, from 2013.


The Problem (Q-score 6, ranked #81st of 95 in the VBA Core archive)

The scenario as originally posted in 2013

I have a userform in Excel that asks for a username and password. Once you enter your password if you press Enter it just “selects” the next item which is the LogIn button, but it doesn’t press it. You have to hit Enter again to actually press the button.

How can I make it so when the user presses enter on his keyboard the LogIn button is pressed and the code associated to is runs (Logincode_click)?

Why community consensus is tight on this one

Across 95 VBA Core entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — niche answer (below median) (+6)

7-line VBA Core pattern (copy-ready)

You could also use the TextBox’s On Key Press event handler:

'Keycode for "Enter" is 13
Private Sub TextBox1_KeyDown(KeyCode As Integer, Shift As Integer)
    If KeyCode = 13 Then
         Logincode_Click
    End If
End Sub

Textbox1 is an example. Make sure you choose the textbox you want to refer to and also Logincode_Click is an example sub which you call (run) with this code. Make sure you refer to your preferred sub


When to Use It — classic (2013–2016)

Ranked #81st in its category — specialized fit

This pattern sits in the 95% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the VBA Core archive for a higher-consensus alternative.

What changed between 2013 and 2026

The answer is 13 years old. The VBA Core object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

This is a below-median answer — when does it still fit?
expand_more

Answer score +6 vs the VBA Core archive median ~4; this entry is niche. The score plus 6 supporting upvotes on the question itself (+6) means the asker and 5 subsequent voters all validated the approach.

Does the 7-line snippet run as-is in Office 2026?
expand_more

Yes. The 7-line pattern compiles on Office 365, Office 2024, and Office LTSC 2026. Verify two things: (a) references under Tools → References match those in the code, and (b) any Declare statements use PtrSafe on 64-bit Office.

Published around 2013 — what’s changed since?
expand_more

Published 2013, which is 13 year(s) before today’s Office 2026 build. The VBA Core object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which VBA Core pattern ranks just above this one at #80?
expand_more

The pattern one rank above is “Create dictionary of lists in vba”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 6, Answer-score 6, original post 2013, ranked #81st of 95 in the VBA Core archive. Last regenerated April 14, 2026.

vba