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.The routine also illustrates the use of the Screen Updating property (code listed above).' --------------------------------------------------------------------------------Sub Open PPSFor Edit() On Error Go To Err Handle Dim p Show As Presentation ' Lock the window to prevent refreshing ' See above article example for the code Screen Updating = False 'Open the show, however use additional flag - With Window set to FALSE Set p Show = Presentations. 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 one particular instance I found an interesting fix: I had a Watch set.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.I was watching the state of an object within the Workbook (the locked property of a specific style).no matter what I did in code to turn off screen updating, it would not work and my app slowed to a crawl.which obviously isn't working because the screen updates a whole lot afterwards. I almost wish this were more complicated; the fact that everything looks so simple is making it difficult to think of what could possibly be happening! So this morning application.screen Updating was working as expected. The test code that I wrote is below: Sub test() Debug. One thing that seems to be common among those modules not working, is that they all contain code that changes worksheets. In any case, it's a real mystery why this happens from one day to another!