I use application.statusbar to keep the users apprised of what is happening.
The status bar will show the message “Macro running” as the code is running, and once the code is done, it will show “Ready” which is one of the default Excel messages. Display Status Bar = True With Worksheets(“Sheet1”) lrow = .
Option Explicit Sub macro1() Dim i As Long, lrow As Long Application.
I have a code that initially sets Screen Updating to False, but in the middle of the code it calls another subroutine and for some reason it actually shows me some (not all) actions (ie, when it selects a new sheet I get to see that). Here is a simplified version of the code Option Explicit Sub Check_Input Data() Application.
I have been following Screen Updating Property through Debug.
You should never have to make a call to things like .activate and .select when automating.
Those are things that excel records in macros, but that can always be circumvented.
So, the debug.prints are correct, reflecting the fact that screen updating is off.
Screen Updating didn't catch any change in the Screen Updating Property? and then put a debug print after the called sub ends and the code returns to the original sub. A selected sheet comes to the top even though screen updating is off.
There's always a object method you can call that does not require and form of screen updating.