VBA Error window has changed - no more Debug button

mcomp72

Active Member
Joined
Aug 14, 2016
Messages
275
Office Version
  1. 365
  2. 2019
  3. 2016
  4. 2011
Platform
  1. Windows
  2. MacOS
I'm not sure how or when this happened, but the look of the VBA error windows I receive has changed. I've created an image to show you what they looked like before, and what they look like now.

VBA-Error-change.png

This is a big problem, because when my code has an error, I can no longer use the Debug button to take me to the line where the error occurred.

I have been working on my Macro-Enabled workbook for several months now, and it did not use to do this. I have no idea what I did to change the way the errors look. As a test, I tried a new workbook, and the error on that one looks the way it should (like the BEFORE image), so it doesn't seem to be a change in Excel itself.

I also tried my workbook on another computer, and the same problem occurred. So I'm guessing there is something in my code that is causing this? I have no idea what it might be. Anyone have any ideas?
 
What if you just put the sub in a sheet module & run it directly, rather than calling it from an event?
 
Upvote 0

Excel Facts

Pivot Table Drill Down
Double-click any number in a pivot table to create a new report showing all detail rows that make up that number
What if you just put the sub in a sheet module & run it directly, rather than calling it from an event?
In that case I get the OK-Help dialog, not the debug button, regardless of whether the sub is Private or not.
 
Upvote 0
That's the same as me, so it looks as though it's always been like that.
 
Upvote 0
That's the same as me, so it looks as though it's always been like that.
Seems that way, and explains why I have never noticed it as my sheet modules are almost exclusively event procedures.
 
Upvote 0
Hmm, I get the debug button if I run that from a selection_change sheet module, or a standard module with the "Break on unhandled errors" setting. XL2010, Win10.

Me too! mine has been set on Break on Unhandled Errors from the git-go. Never had a problem with missing buttons. Maybe it's just grimlins.
 
Last edited:
Upvote 0
I don't get the debug button if running the code from a sheet module with Break on Unhandled Errors (which is what I always have it set as), I do get the button in a regular module with Break on Unhandled Errors (or a sheet module with break on all errors or break in class module).

Also running 365 on W10 same as Fluff so might be a 365 issue.
 
Upvote 0

Forum statistics

Threads
1,214,655
Messages
6,120,760
Members
448,991
Latest member
Hanakoro

We've detected that you are using an adblocker.

We have a great community of people providing Excel help here, but the hosting costs are enormous. You can help keep this site running by allowing ads on MrExcel.com.
Allow Ads at MrExcel

Which adblocker are you using?

Disable AdBlock

Follow these easy steps to disable AdBlock

1)Click on the icon in the browser’s toolbar.
2)Click on the icon in the browser’s toolbar.
2)Click on the "Pause on this site" option.
Go back

Disable AdBlock Plus

Follow these easy steps to disable AdBlock Plus

1)Click on the icon in the browser’s toolbar.
2)Click on the toggle to disable it for "mrexcel.com".
Go back

Disable uBlock Origin

Follow these easy steps to disable uBlock Origin

1)Click on the icon in the browser’s toolbar.
2)Click on the "Power" button.
3)Click on the "Refresh" button.
Go back

Disable uBlock

Follow these easy steps to disable uBlock

1)Click on the icon in the browser’s toolbar.
2)Click on the "Power" button.
3)Click on the "Refresh" button.
Go back
Back
Top