I always turn off screen updating when I run a macro that does more than look at one cells value and return it.
In my experience screenupdating significantly slows Excel because it has to calculate each time you do something.
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 set it to "All procedures" and "All modules" for the context, ran the procedure as usual in debug mode, then deleted the watch, closed the VB Code editor, and it was back to normal, the screen not being updated as my code was stating properly! I was able to solve my issue by deleting the Application. It appears that there is no single solution to this problem.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.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.Check other procedures that are called within your current one to check if they are changing your Application. However, as soon as I removed the watch, it worked fine. I ran into this problem a few times myself recently. Screen Updating = True Try running it and you should see a short pause followed by column A getting filled with numbers.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.Screen Updating behaves as a procedure-level application property.As soon as my code leaves the procedure where Application.I started to debug, and immediately after the "Screen Updating = false" line executes, I go to the immediate window and type: Debug. Any clues on how to solve it would be greatly appreciated. Screen Updating = True End Sub _________________________________________________________ Private Sub Check_for_Open_Workbook() Application. 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.