In this thread:
https://www.mrexcel.com/forum/excel...excel-2016-screen-flickering.html#post5049484
... I was given the advice to use Application.ScreenUpdating = False on my entire code to prevent screen flashing/flickering while running the code (this issue started when upgrading from Office 2010 to Office 2016).
But my code opens and closes a lot of wb's during it's run, and I've now discovered that Application.ScreenUpdating = False may not be enough to keep all wb's down while running the code. It seems that Excel 2013/2016 creates new instances when I open a file, and these wb's ain't affected.
Anyone that knows of a way I can prevent this using vba?
In my code I've also started using Application.StatusBar = "Currently updating file: Group1" and so on to let me know what my code is currently doing, but when other wb's still pop up I'm losing this information as well...
https://www.mrexcel.com/forum/excel...excel-2016-screen-flickering.html#post5049484
... I was given the advice to use Application.ScreenUpdating = False on my entire code to prevent screen flashing/flickering while running the code (this issue started when upgrading from Office 2010 to Office 2016).
But my code opens and closes a lot of wb's during it's run, and I've now discovered that Application.ScreenUpdating = False may not be enough to keep all wb's down while running the code. It seems that Excel 2013/2016 creates new instances when I open a file, and these wb's ain't affected.
Anyone that knows of a way I can prevent this using vba?
In my code I've also started using Application.StatusBar = "Currently updating file: Group1" and so on to let me know what my code is currently doing, but when other wb's still pop up I'm losing this information as well...
