Screen Updating = False , and this is how I solved it: I found that Application.Screen Updating behaves as a procedure-level application property.Check other procedures that are called within your current one to check if they are changing your Application. However, as soon as I removed the watch, it worked fine. I ran into this problem a few times myself recently.

Screen Updating = false" because I saw the yellow highlight go over the line in debug mode. Calculation = xl Calculation Automatic Application. Screen Updating from within the code instead of the immediate window, but I'm fairly sure what I'll find. This function gets called by an event handler that catches a Commands Bar button event (? Basically, we create a menu bar and one of the buttons in our custom "File" menu is labeled "Load Portfolio" which calls this function. I have encountered the same symptoms and can't think as to why it's happening. I think that maybe something has broken in my excel because even when I closed out of excel and opened a brand new 2003 workbook with no previous code I was getting the same problem. The interesting thing is that *some* of my modules allow Screen Updating to be set to False, there's only a few that don't.

However, I *can* change the Screen Updating from the immediate window. Screen Updating = False b Global Change Event = True Application. About to go home for the day, but I plan on trying to print Application. So while Screen Updating always is True in debug mode, this is not the issue for me.

Yes indeed, the screen continues to be updated so that you can see the changes happen, but the value of this variable DOES CHANGE effectively. YES I remember that when I brought the last change to my code, I had indeed set a watch, but since I am working on customizing the ribbon, I save and close very often my excel file and I have certainly not deleted all the watches before posting my updates to prod.

Hence, what I did is to follow tjeffryes' recommendation and created a new watch on any variable.

Screen Updating = False" statement) while the "Application.

Enable Events" was changing from True to False, so all the people who say that in debug mode it never changes, this is not right to say that!

To solve, for each procedure, and called procedures, that I wanted to run with Screen Updating set to False, I "bookended" my procedure and its called procedures with the Screen Updating code at the top and bottom of each procedure. Screen Updating = False Call Secondary_Procedure Application. Screen Updating = True End Sub I am having the same problem.

Screen Updating = True End Sub ****** Sub Secondary_Procedure Application. I have a macro that reads info from one workbook and updates another.

As soon as my code leaves the procedure where Application.