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.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.
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.
Screen Updating = True Try running it and you should see a short pause followed by column A getting filled with numbers.
Screen Updating = False , and this is how I solved it: I found that Application.
Screen Updating behaves as a procedure-level application property.
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.
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.
Screen Updating = False" statement) while the "Application.
Enable Events" was changing from True to False, so all the people who say that in debug mode it never changes, this is not right to say that!
Don’t forget to set your Screen Updating property back to True when you’re done.