How to trace macros

[Bluejay906]

I use macros very rarely. I have this application I inherited that uses macros very heavily. This has caused some issues but this one is a doozie. I made a change in the system and had to modify a report. I changed the name. When I try to run the report from a report, a macro launches. What is odd is that an error occurs for a macro not part of the particular group. If this were VBA, I would put in break points to see where the failure occurs. I am not sure how to do this for macros. Are there any macro mavens out there who can assist?

Thanks.

[missinglinq]

Well, you've discovered the two of the three major reasons for not using macros! They're cryptic; it's a real pain to go inside and see what they do (as opposed to simply going into one code editor). And they allow no Error Handling! The third reason is that they're very limited in what they can do and how they do it!

Without knowing exactly what chagnes you've made, or how your db is set up, it's difficult to say exactly what's going on. My guess is that the macro you're using is calling another macro, which is where the error is occuring. As to "tracing macros" you can either open each macro in Design View to see what it does or use the Documenter.

Goto Tools - Analyze - Documenter - Macros
Click on SelectAll then OK.

Good Luck!

Linq