Not hitting breakpoints!...

[cmyers65]

I have breakpoints in a procedure called TestMain() located in Module 22. I call TestMain() from the procedure Worksheet_Change() located in Sheet1. I can hit my breakpoints in Worksheet_Change() but not in TestMain(). Does anyone know why this is?...

Both Module22 and Sheet are from the project StartChart.xlsm...

I can run TestMain() via Run->RunSub/UserForms and select TestMain. When I do this I do hit all the breakpoints...

When I don't hit the breakpoints running form Worksheet_Change(), I know it is running TestMain() do to the MsgBox messages being displayed...

If anyone has any suggestions I would be most appreciative!

[MarvinP]

Hi cmyers65 and welcome to the forum,

If your subroutine in Module22 (called TestMain()) was in an if condition in the Private Sub like:

Please Login or Register  to view this content.

then TestMain wouldn't be called.

Another possibility is that the worksheet didn't really change so the Event Code was never called.

Hope that helps.

[cmyers65]

I've proved I'm getting to the Run command by adding MsgBox calls. I also can see I'm calling the routine because I put a MsgBox call into the called routine. I just DON'T get to stop the code with a breakpoint!!! Here's more detail. I stripped down the code to nothing and it still doesn't run.

Here's the code:

In Sheet1(Sheet1):

Please Login or Register  to view this content.

I set breakpoint at the 'Run "TryMain()"' line above.

Module22:

Please Login or Register  to view this content.

I set a breakpoint at the 'MsgBox"Here I am in TryMain()"' line above.

Within Excel I have the spreadsheet up for Tab 1 named Sheet1.
I edit the Cell at location B1.
I reach the breakpoint in the Worksheet_Change procedure in Sheet1 at the 'Run "TryMain()"' line.
I then press F5 to continue running.
I don't reach the breakpoint in the TryMain procedure in Module22 at the 'MsgBox "Here I am..."' line.
I do get to the message box and hit ok. I just don't sit at the breakpoint...

I cross posted to Mr. Excel... Here is the link: http://www.mrexcel.com/forum/showthread.php?t=521170

[DonkeyOte]

@cmyers, appreciate you're a new member but please note:

1 - use CODE tags to encase your VBA at all times

2 - more importantly - if you cross post the same question on other Excel message boards (say MrExcel for ex.) you must provide links

Please be sure to read & familiarise yourself with the Forum Rules before posting further.

[MarvinP]

Try the below without quote marks instead of Run with quotes

Please Login or Register  to view this content.

[Nickneem]

You could try to export and import all your forms, modules and class modules, your code could be corrupt.
Do it manually or use this tool:
http://www.appspro.com/Utilities/CodeCleaner.htm

And in the VBE --> Debug - Compile project.

I experienced more or less the same this morning, breakpoints not hit, forms unexpectedly closed..

Add.. Turned out my excel / code went unstable after clicking a checkbox which cleared a text from a bound combobox.
The combobox had a rowsource (=BRONNEN!GENRNGGlaskleur)
Private Sub chkGlasFront_Click()
cmbglas.text = ""
End Sub

Clicking the checkbox caused an unload of the form (not intented) / crashed the form and after that breakpoints weren't hit...


G'luck

Mike D

[cmyers65]

MarvinP, thanks for your input. That did the trick!! I'm reposting your solution so that I can play with code tags. I didn't use them and want to make sure I know how to. Thanks again!

The solution was this:

Please Login or Register  to view this content.

[cmyers65]

Do you know why calling TryMain() using the run command makes the breakpoints not work? And why using the call command instead fixes this?

[MarvinP]

Hi cmyers65, here is my best answer.

Go into the vba editor and search for RUN and read the section on Application.Run.
In the remarks it claims:

You cannot use named arguments with this method. Arguments must be passed by position. Objects passed as arguments to the macro are converted to values (by applying the Value property to the object). This means that you cannot pass objects to macros by using the Run method.

Somehow I believe the above comes into play while CALL does not.