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!
Thanks to tjeffryes' remark, I checked if I had any watch set and I didn't... Well, the function is quite long, but you're looking at the function's entry point. The immediate window says True, then False, then True again as expected, but the code doesn't seem to have any effect on the application. If all of this happens, then you know it is working correctly. Net 2003 and Office 2010 Code: Excel Graphing | Excel Timer | Excel Tips and Tricks | Add controls in Office | Data tables in Excel | Gaussian random number distribution (VB6/VBA, VB. Screen Updating = False If my Debug = False Then On Error Go To Error Handler I'm afraid that's pretty much it. Screen Updating End Sub As I step through the code when I hove over Application.screen Updating it always says True. Then put it in debug mode and step through with screen updating turned off again, you should find that you still see the numbers going in one by one.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.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).A common reason why this problem occurs is when your code calls for code in a different procedure. Screen Updating is turned on outside of the procedure. ________________________________________________________ Private Sub Clock_In() Application. Enabled = True Check_for_Open_Workbook Sheets("Time Log"). no matter what I did in code to turn off screen updating, it would not work and my app slowed to a crawl. 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. All those Screen Updating = False's you see is called "sheer desperation". I can still enter the workbook and it is screenupdating away even right after the line set it false. Screen Updating = False" in the immediate window it works as expected. Thanks Colin Correct, when you step through in debug mode the screenupdating remains turned on. To test it properly, try this: Put a commandbutton on your sheet and paste in Application. Net) | Coordinates, Vectors and 3D volumes I've experienced this problem, with code that previously worked!Application.screenupdating = False was not stopping the screen update when it was call straight in an event. Screen Updating = False On Error Go To Open_Workbook1 Windows("Time M.xls"). Screen Updating = True I have had this same problem... I ran into this problem a few times myself recently.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.