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.
In my case, when adding Application.screenupdating = False in my Workbook_Before Save code, it did not do it's job. yes a common occurrence is when you call another piece of code. In one particular instance I found an interesting fix: I had a Watch set.
I re-insist as well on the fact the "NO there was no call to another sub procedure setting it to "True" because when debugging my procedure, I could clearly see the value of "Application.
Screen Updating" not changing from True to False (thus being TRUE before and staying to TRUE right after the "Application.
When we set Screen Updating property of an application object to false then it will speed up the macro. Please find the below example for Screen Updating Property of an application object in excel VBA.
Explanation: In the above example, it will display numbers from 1 to 100 in the first column on Sheet1.
I was watching the state of an object within the Workbook (the locked property of a specific style).