Forum Discussion
Application.ScreenUpdating
This only occurs in Excel 2013 and Excel 2016.
Typical use for Application.ScreenUpdating would be to supress screen flicker during opening and transfer of data to another workbook. Without this property, the second workbook becomes the active element and the primary window. Even providing the instruction to 'Activate' the first workbook immediately after opening the second still transfers the primary window to the second momentarily.
This becomes even more evident if cell data is moved from one workbook to another.
Using Application.ScreenUpdating in Excel 2010 does exactly as intended and locks the screen while processes such as those described run.
The reason for that might be the SDI (Single Document Interface) that was first introduced in Excel 2013.
Please read this https://msdn.microsoft.com/en-us/vba/excel-vba/articles/programming-for-the-single-document-interface-in-excel?f=255&MSPPError=-2147217396 for more information about it.
Yes, I see where you are going but as the two open workbooks are in the same instance and active within their own window environment the application property should still be effective on the primary display.
It does state: "all of the Excel application-level window methods, events, and properties remain unaffected and work the way they have in previous versions of Excel", so this implies 'ScreenUpdating' should be the same.
I still don't understand why Microsoft have not answered this question considering the number of references that can be seen just by putting this inquiry into a web browser. Plus, what are all those Excel application developers using 'ScreenUpdating' doing when used in 2013/2016?
Someone has reported this problem to Microsoft in the Excel’s suggestion box.
Please check it https://excel.uservoice.com/forums/304921-excel-for-windows-desktop-application/suggestions/18688627-vba-screenupdating-property-does-not-work-in-excel and vote for it as I did.
David,
I have Excel 2010 and Excel 2016 both installed on my PC, so can you provide a code example to be able to reproduce this issue on my own?
Anyway, I recommend you to ask this https://answers.microsoft.com/en-us/msoffice/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1 instead because it's the best place to get support for such an issue.