Vba excel screenupdating dating mid twenties
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.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).Screen Updating" not changing from True to False (thus being TRUE before and staying to TRUE right after the "Application.Screen Updating = False" statement) while the "Application.Screen Updating = False was set, it's value resets to True.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.In one particular instance I found an interesting fix: I had a Watch set.
Then comment out the line which turns off screen updating and see what happens; you should find that you scroll down the sheet as the numbers get filled.
I really hope this will help some other people coming here for the same issue since indeed, this is the kind of things very time consuming and going you crazy! yes a common occurrence is when you call another piece of code. Each person may be experiencing it for a different reason.
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. Just try everything on this page and see if it works for you!
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.