Run excel VBA function when sheet is clicked

calendar_today Asked Oct 24, 2011
thumb_up 7 upvotes
history Updated April 14, 2026

Direct Answer

Double click the "Workbook" icon in VBE and use this event. It will trigger everytime you activate a different sheet by clicking its tab. If the tab is the one named "View…. This is a 8-line VBA Core snippet, ranked #75th of 95 by community upvote score, from 2011.


The Problem (Q-score 5, ranked #75th of 95 in the VBA Core archive)

The scenario as originally posted in 2011

I was wondering if there was a way to run a VBA script when I open a sheet in the workbook.

For example, I have a workbook called “Inventory” and I want to run an “InitiateInventoryValues” Function when the “View Inventory” sheet is opened.

Can anybody please help me on this?

Why this Range / Worksheet targeting trips people up

The question centers on reaching a specific cell, range, or workbook object. In VBA Core, this is the #1 source of failures after activation events: every property (.Value, .Formula, .Address) behaves differently depending on whether the parent Workbook is explicit or implicit.


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

8-line VBA Core pattern (copy-ready)

Double click the “Workbook” icon in VBE and use this event. It will trigger everytime you activate a different sheet by clicking its tab. If the tab is the one named “View Inventory”, your code will run (once) when the sheet is activated:

Private Sub Workbook_SheetActivate(ByVal Sh As Object)

If Sh.Name = "View Inventory" Then
    'Do your code
End If

End Sub


When to Use It — vintage (14+ years old, pre-2013)

Ranked #75th in its category — specialized fit

This pattern sits in the 94% 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 2011 and 2026

The answer is 15 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 +7 vs the VBA Core archive median ~4; this entry is niche. The score plus 5 supporting upvotes on the question itself (+5) means the asker and 6 subsequent voters all validated the approach.

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

Yes. The 8-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.

This answer is 15 years old. Is it still relevant in 2026?
expand_more

Published 2011, which is 15 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 #74?
expand_more

The pattern one rank above is “User Defined Functions NOT recalculating”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 5, Answer-score 7, original post 2011, ranked #75th of 95 in the VBA Core archive. Last regenerated April 14, 2026.

vba