BeforeClose code working in debug but sporadically in actual execution - how can I test it

Every time I try to debug it using the ways I'm familiar with (stepping through the code, breaking out and testing pieces of code) it works fine. I get no error message when it doesn't work, I just reopen the file and the rows that should have been deleted weren't. When I try it a second time it works fine.

When you step through the code to completion, are the changes saved? Upon reopen, you see what you should see?

Throwing out some ideas to see what sticks.

Can you determine in your debugging if the cleanup happens but it's not saved, or if the cleanup doesn't happen and it is saved, or both the cleanup and save don't happen?


With this code...

Please Login or Register  to view this content.

If you have more than one workbook open, the ActiveWorkbook may not be the same as ThisWorkbook. Are you saving the right workbook here.



Where do you declare bDoNotRun? Is it in a standard code module (e.g.; Module1) and declared as Public? Can you monitor bDoNotRun? One possibility is that it's getting set to True on one occasion then later not reset back to False when you want to cleanup.

GeneralDisarray - yes, if I step through the code completely it does all of the coded deletions and other pieces with no issues. I can stop just about anywhere and step through it (I've tried just about every stop point I can think of) and then let it run past that point (F5) and it will work as designed. It will also work as designed if I F8 through every single step (uber tedious but I had to do it to be sure!)

AlphaFrog - I feel like I'm responding to a celebrity I see your name here so often in my searches! I thought that since the userform was in the correct workbook that it would force the active workbook to be the correct one but I can certainly change that to make it safer.

bDoNotRun was my best guess as to the culprit as well but I don't think I've tested it/debugged it thoroughly so it's well worth another look. I declare it as a Public function in my function module (just a regular module - I named a module for functions, one for main code and one for just admin stuff/testing)

Please Login or Register  to view this content.

I'll watch bDoNotRun and see if anything funky is happening there and then report back.

Thank you both VERY much for trudging through that code!