In one particular instance I found an interesting fix: I had a Watch set.
I was watching the state of an object within the Workbook (the locked property of a specific style).
Thanks to tjeffryes' remark, I checked if I had any watch set and I didn't...
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.
As there is no command in Excel to refresh a worksheet in the way a user form can be refreshed, it is necessary to use a trick to force Excel to update the screen.
When I moved the code I wanted to run before save to it's own module, then called the module from Workbook_Before Save, it worked like a charm...(events disabled in module, so additional sheet level events did not trigger) Hoping this will help someone else out - drove me crazy for a while!!! Caption = "Ready to clock out of last task." Command Button2. I was killing myself over why the heck screen updating was not set to false!!!! I solved my problem with a very simple solution: At the very very end of the code put: Application. I was watching the state of an object within the Workbook (the locked property of a specific style). 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. Sub load Portfolio() Dim i Test As Integer, portfolio Version As String Application. :-) Basically, after all those statements (and between each one) Screen Updating remains "True". Screen Updating = False For i = 1 To 10000 Worksheets("Sheet1"). Screenupdating = False worked perfectly in Excel 2007 until last week, when it remained True however many times I tried to set it to False.A User Form will not be refreshed in some cases, because Do Events will fire the events; however, Repaint will update the User Form and the user will see the changes on the screen even when another event immediately follows the previous event.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!