StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>As requested in comments...</p> <p>Look up the 'Caller' property of the 'Application' object in the Excel VBA help. When you use it from a VBA routine, it will tell you where the call to the routine came from - what Range, Chart, etc.</p> <p>An important thing to be aware of when using 'Application.Caller' is that it isn't always a Range object. Look at the help, but the property returns a Variant value that can be a Range, String, or Error. (It is a Range object in the case you're interested in, but you'll need to be aware of this.)</p> <p>Because of the above, and the vagaries of VBA syntax when it comes to objects vs. values, it can be tricky to use 'Application.Caller'. Putting a line like:</p> <pre><code>Debug.Print Application.Caller.Address </code></pre> <p>in your code will fail when the caller isn't a Range. Doing something like:</p> <pre><code>Dim v v = Application.Caller </code></pre> <p>will "compile", but will create circular references when the caller <em>is</em> a Range because you're trying to access the value of the calling Range.</p> <p>This all means that it's probably best to write a little utility function for yourself:</p> <pre><code>Public Function currentCaller() As String If TypeOf Application.Caller Is Range Then Dim rng As Range Set rng = Application.Caller currentCaller = rng.Address(External:=True) Else currentCaller = CStr(Application.Caller) End If End Function </code></pre> <p>and then call it from your error handlers where you want to know where the call came from.</p> <p>One more thing - obviously this can only tell you the caller once a VBA routine has actually been called. If you have errors in your calling formulas, Excel will return error values to your cells without ever calling your VBA routines.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload