Is there a way to have a running printout of the stack, and possibly the points where one procedure hands off or calls another? A project I have been working on for well over a year now has become hard to manage. When I run some procedures I note that some called subs, whether directly called, called from other called subs, called from change events or anyway else get repeatedly called, some unnecessarily a number of times before the code executed finally returns control back to the user (me). This primarily happens when calculating or recalculating values that fill in the forms I display to keep track of the work I do. I am looking for ways to analyze the execution from when I trigger code to start running untill when it stops and returns control to the user, but the code has become awfully involved.
I am hopeful that there might be means to do this directly within the VBE, for as can be seen with my previous posts, I am quite capable of missing the painfully obvious. If not available through the VBE, are there outside programs that anyone can recommend having used any?
I think I have shown myself the true meaning of "spaghetti code", as much as I have tried to develop good practices, and wish to start digging my way out.
Thank-you for your consideration and lending your knowledge!
Bookmarks