Get name of an Excel worksheet containing code

calendar_today Asked Aug 8, 2013
thumb_up 5 upvotes
history Updated April 14, 2026

Direct Answer

Use the "Me" object. Me.Name is the property you seek, wich will give you the name of the sheet containing the code regardless the active sheet. This is a prose walkthrough, ranked #286th of 303 by community upvote score, from 2013.


The Problem (Q-score 6, ranked #286th of 303 in the Excel VBA archive)

The scenario as originally posted in 2013

I have code that resides on a page and references the content of the workbook. When executed from a different worksheet, I would like to get the name of the specific Worksheet containing the code.

I have worksheets that contain data. The code is added to that worksheet and the run – which produces a Summary worksheet. From the Summary worksheet, I would like to run the code on the data worksheet. This means I can’t use ActiveSheet and I would have to reference the data sheet by name.

How can I get the name of the worksheet containing the code without having to hard-code the name?

Why community consensus is tight on this one

Across 303 Excel VBA 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) (+5)

Verbal answer — walkthrough without a code block

Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Excel VBA entries ranked in the top 10 of the same archive.

Use the “Me” object.

Me.Name is the property you seek, wich will give you the name of the sheet containing the code regardless the active sheet.


When to Use It — classic (2013–2016)

Ranked #286th in its category — specialized fit

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

What changed between 2013 and 2026

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

The answer has no code block — how do I turn it into a snippet?
expand_more

Use the walkthrough above as a checklist, then open a top-10 Excel VBA archive entry for a concrete starting template you can adapt.

Published around 2013 — what’s changed since?
expand_more

Published 2013, which is 13 year(s) before today’s Office 2026 build. The Excel VBA 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 Excel VBA pattern ranks just above this one at #285?
expand_more

The pattern one rank above is “xlrd original value of the cell”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 6, Answer-score 5, original post 2013, ranked #286th of 303 in the Excel VBA archive. Last regenerated April 14, 2026.