Platforms; IT settings; UDFs; fatal errors occurring from unforeseen reasons (but they’d seem obvious after they happen when first unforeseen); the list goes on. I cannot tell you how many times in my work I’ve come across a potential bad outcome were the True setting not reset.
Whether the end of a macro comes from the expected process of events or through error handling, please always ensure you have reset Screen Updating to True if you had previously set to False.
It happens when there is transition among excel files.
The same macro worked properly in win 7 with office 2010.
Future versions of Excel will invariably support new, or stop supporting existing, VBA methods and properties, so it’s an unnecessary risk to not reset Screen Updating.
If you change the setting of something, then when you are through, set it back to the way it was before. There are too many bad possible outcomes that you would not know about until they happen.
Simply add the following code line to achieve this.
Many of the properties and methods that return the most common user-interface objects, such as the active cell (Active Cell property), can be used without the Application object qualifier.
There is a word that you can use with Application that will neutralise all the alerts that Excel can send your way.
Discover this word and many others that you can use in combination with Application in the downloadable course on Excel macros. As you can read: starting in cell A1 a value of "99" will be entered in the selected cell then the cursor will move one cell down to enter "99", repeat the process until the row number of the selected cell is 3000 and come back to cell A1.