The Problem (Q-score 7, ranked #154th of 303 in the Excel VBA archive)
The scenario as originally posted in 2013
Is there a way to get a list of all valid properties for a given object?
If I wanted to start at cell a1, and go down and assign a1, a2, a3, all of the valid properties for let’s say a worksheet object for example, is that something that can be done? I can’t find any:
list = object.enumproperties
Any ideas?
Why this Range / Worksheet targeting trips people up
The question centers on reaching a specific cell, range, or workbook object. In Excel VBA, 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) (+9)
16-line Excel VBA pattern (copy-ready)
Tools – References – TypeLib Information.
Then:
Sub DumpProperties(ByVal o As Object)
Dim t As TLI.TLIApplication
Set t = New TLI.TLIApplication
Dim ti As TLI.TypeInfo
Set ti = t.InterfaceInfoFromObject(o)
Dim mi As TLI.MemberInfo, i As Long
For Each mi In ti.Members
i = i + 1
ActiveSheet.Cells(i, 1).Value = mi.Name
Next
End Sub
Loop-performance notes specific to this pattern
The loop in the answer iterates in process. On a 2026 Office build, setting Application.ScreenUpdating = False and Application.Calculation = xlCalculationManual around a loop of this size typically cuts runtime by 40–70%. Re-enable both in the Exit handler.
When to Use It — classic (2013–2016)
Ranked #154th in its category — specialized fit
This pattern sits in the 97% 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.