VBA Error window has changed - no more Debug button

[mcomp72]

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.

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?

 

[DanteAmor]

I'm sorry, I understood, the debug button was lost

I guess something in your version of excel-vba was updated.

 

[ZVI]

Hi ZVI. I'm not sure I understand what you're saying. But I did what I think you're suggesting.

I searched my entire project for "vbMsgBoxHelpButton" but it was not found. So there does not appear to be any code in my file similar to what you've posted.

In ran Debug -> Compile from the VBE, but it did not find any problems.

Thanks for testing, have no good ideas then.
May be something is damaged in the workbook structure or in VBA compiled chains.
If possible please share that workbook for analyzing without sensitive data.

 

[DanteAmor]

If the project is password protected, then the debug button does not appear, since the code is not enabled until the correct password is entered.

 

[DanteAmor]

Apparently it's an editor error, check the following:

https://answers.microsoft.com/en-us...g/e0c38c46-9d27-4330-86ae-b20606d6bf9f?page=2

 

[mcomp72]

ZVI, unfortunately I'm not comfortable posting my workbook publicly, because it's something I plan to release as a commercial project one day, so I don't want a "free" copy floating out there with the source code easily viewable.

Is there a way for me to check to see if the file is damaged in some way? Or is this something that is very difficult to do?

 

[mcomp72]

DanteAmor -- the thing is, if I create a new workbook, this problem does not happen. On a new workbook, I get the correct error window with the Debug button on it, just as I should. The problem only seems to be with this particular workbook. It did not use to do this. I only noticed it today.

 

[DanteAmor]

DanteAmor -- the thing is, if I create a new workbook, this problem does not happen. On a new workbook, I get the correct error window with the Debug button on it, just as I should. The problem only seems to be with this particular workbook. It did not use to do this. I only noticed it today.

If you don't have a password in the project, then you could copy the data from each sheet to the new book and also copy modules and userform to the new book.

When a sheet or book is damaged, sometimes it is not known what the problem is and everything has to be passed to a new book.

 

[mcomp72]

I just discovered something I had not noticed before. I only get the different error window (the one without the Debug button) if the error is occurring inside a sheet module. If an error occurs in a regular module, I DO get the error window with the Debug button. Is this how Excel VBA normally behaves? I don't remember it being that way, but maybe I just don't remember it correctly? Can someone else let me which kind of error window they get if they encounter a run-time error in a sheet module? I'd be very curious to hear.

 

[JoeMo]

I just discovered something I had not noticed before. I only get the different error window (the one without the Debug button) if the error is occurring inside a sheet module. If an error occurs in a regular module, I DO get the error window with the Debug button. Is this how Excel VBA normally behaves? I don't remember it being that way, but maybe I just don't remember it correctly? Can someone else let me which kind of error window they get if they encounter a run-time error in a sheet module? I'd be very curious to hear.

I get the debug run time error dialog box when I run the sheet code below.

Private Sub Worksheet_SelectionChange(ByVal Target As Range)
Dim R As Long
'Next line generates runtime error if the sheet does not contain the string "BIG ERROR"
R = Cells.Find("BIG ERROR").Row
End Sub

 

[Fluff]

If I run JoeMo's code I also get the standard dialog box, using 365 on Win10