Mapping the macro path

[Daniel Bonallack]

Is there a tool to map the path a macro takes through all it's procedures?

I have done a particularly ugly job of creating a macro-intensive
spreadsheet over the past 3 years. In fact, I challenge you to think of a
single VBA-Best-Practive that I have competently implemented in this
spreadsheet. Truly, I should be sent to Notepad and told to stay there for
the rest of my life. I would have gotten away with my abuse, but now I have
to share the spreadsheet with a more proficient programmer.

But perhaps you can help. Is there a tool that will map the complex paths
taken by the various procedures when the start button is pushed?

Or, failing that, is there a single line of code that I can copy to every
procedure that will return the procedure name to a cell as it runs?
Something like:

Sheets("MapPath").Range("A1").end(xlDown).offset(1,0).value =
CurrentMacro.Name

Any help appreciated.

regards
Daniel

 

[StumpedAgain]

Hi Dan,

Two easy ways to monitor what your macro is doing is using the step function
(found in the debug toolbar) and the other is using "breakpoints" by right
clicking the small space between the project viewer and the macro area.
Stepping through (also you can use "F8") goes through the program step by
step and the breakpoints stop the code so you can see where things are at
wherever the code reaches the breakpoint. Whenever you're in the middle of
the code, you can hover your mouse over different variables and procedures to
see which values are assigned to different code.

Hope this helps!!

PS. Any code that works is good code. Someone may be able to make it look
better or run a little faster, but working code is good code.

 

[Bob Phillips]

Daniel,

I have some code that adds a procedure name to all procedures, it could
easily be adapted to write a trace statement in the procedure instead.

Drop me an email offline, saying whether you want it to write to the debug
window (may overflow quickly), a spreadsheet, a text file or whatever, and I
will knock you up a little prototype.

BTW, that will teach you to employ more proficient coders <g>.

 

[Daniel Bonallack]

Thanks Bob! Will e-mail you now.

Daniel,

I have some code that adds a procedure name to all procedures, it could
easily be adapted to write a trace statement in the procedure instead.

Drop me an email offline, saying whether you want it to write to the debug
window (may overflow quickly), a spreadsheet, a text file or whatever, and I
will knock you up a little prototype.

BTW, that will teach you to employ more proficient coders <g>.

--
__________________________________
HTH

Bob