Home

Application.ScreenUpdating

%3CLINGO-SUB%20id%3D%22lingo-sub-228819%22%20slang%3D%22en-US%22%3EApplication.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-228819%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20seen%20the%20other%20posts%20on%20this%20topic%2C%20where%20the%20property%20does%20not%20function%20in%20Excel%202016%2C%20but%20there%20still%20does%20not%20appear%20to%20be%20a%20remedy%20for%20this%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%2C%20like%20probably%20thousands%20of%20vba%20writers%20are%20now%20finding%20their%20Excel%202010%20(or%20earlier)%20macros%20employing%20this%20property%20to%20suppress%20screen%20flicker%20(and%20jumping%20between%20workbook%20windows)%20now%20make%20their%20applications%20look%20very%20%3CSPAN%3Eamateurish%3C%2FSPAN%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWith%20so%20many%20questions%20and%20comments%20since%20the%20release%20of%20Excel%202013%2C%20when%20this%20issue%20first%20occurred%2C%20there%20has%20not%20been%20an%20explanation%20from%20Microsoft%20as%20to%20why%20this%20property%20has%20been%20disabled%20and%20more%20importantly%20whether%20you%20accept%20with%20the%20level%20of%20concern%20a%20fix%20is%20required.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20can%20you%20explain%20and%20how%20users%20can%20overcome%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-228819%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMacros%20and%20VBA%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-233744%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-233744%22%20slang%3D%22en-US%22%3E%3CP%3ESomeone%20has%20reported%20this%20problem%20to%20Microsoft%20in%20the%20Excel%E2%80%99s%20suggestion%20box.%3C%2FP%3E%3CP%3EPlease%20check%20it%20%3CA%20href%3D%22https%3A%2F%2Fexcel.uservoice.com%2Fforums%2F304921-excel-for-windows-desktop-application%2Fsuggestions%2F18688627-vba-screenupdating-property-does-not-work-in-excel%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20and%20vote%20for%20it%20as%20I%20did.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-229391%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-229391%22%20slang%3D%22en-US%22%3E%3CP%3EDavid%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20Excel%202010%20and%20Excel%202016%20both%20installed%20on%20my%20PC%2C%20so%20can%20you%20provide%20a%20code%20example%20to%20be%20able%20to%20reproduce%20this%20issue%20on%20my%20own%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway%2C%20I%20recommend%20you%20to%20ask%20this%20%3CA%20href%3D%22https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%3Fsort%3DLastReplyDate%26amp%3Bdir%3DDesc%26amp%3Btab%3DAll%26amp%3Bstatus%3Dall%26amp%3Bmod%3D%26amp%3BmodAge%3D%26amp%3BadvFil%3D%26amp%3BpostedAfter%3D%26amp%3BpostedBefore%3D%26amp%3BthreadType%3DAll%26amp%3BisFilterExpanded%3Dfalse%26amp%3Bpage%3D1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ecommunity%3C%2FA%3E%20instead%20because%20it's%20the%20best%20place%20to%20get%20support%20for%20such%20an%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-229359%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-229359%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20I%20see%20where%20you%20are%20going%20but%20as%20the%20two%20open%20workbooks%20are%20in%20the%20same%20instance%20and%20active%20within%20their%20own%20window%20environment%20the%20application%20property%20should%20still%20be%20effective%20on%20the%20primary%20display.%3C%2FP%3E%3CP%3EIt%20does%20state%3A%20%22all%20of%20the%20Excel%20%3CEM%3Eapplication-level%3C%2FEM%3E%20window%20methods%2C%20events%2C%20and%20properties%20remain%20unaffected%20and%20work%20the%20way%20they%20have%20in%20previous%20versions%20of%20Excel%22%2C%20so%20this%20implies%20'ScreenUpdating'%20should%20be%20the%20same.%3C%2FP%3E%3CP%3EI%20still%20don't%20understand%20why%20Microsoft%20have%20not%20answered%20this%20question%20considering%20the%20number%20of%20references%20that%20can%20be%20seen%20just%20by%20putting%20this%20inquiry%20into%20a%20web%20browser.%20Plus%2C%20what%20are%20all%20those%20Excel%20application%20developers%20using%20'ScreenUpdating'%20doing%20when%20used%20in%202013%2F2016%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-229310%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-229310%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20reason%20for%20that%20might%20be%20the%20SDI%20(Single%20Document%20Interface)%20that%20was%20first%20introduced%20in%20Excel%202013.%3C%2FP%3E%3CP%3EPlease%20read%20this%20%3CA%20href%3D%22https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fvba%2Fexcel-vba%2Farticles%2Fprogramming-for-the-single-document-interface-in-excel%3Ff%3D255%26amp%3BMSPPError%3D-2147217396%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Earticle%3C%2FA%3E%20for%20more%20information%20about%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-228962%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-228962%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20only%20occurs%20in%20Excel%202013%20and%20Excel%202016.%3C%2FP%3E%3CP%3ETypical%20use%20for%20Application.ScreenUpdating%20would%20be%20to%20supress%20screen%20flicker%20during%20opening%20and%20transfer%20of%20data%20to%20another%20workbook.%20Without%20this%20property%2C%20the%20second%20workbook%20becomes%20the%20active%20element%20and%20the%20primary%20window.%20Even%20providing%20the%20instruction%20to%20'Activate'%20the%20first%20workbook%20immediately%20after%20opening%20the%20second%20still%20transfers%20the%20primary%20window%20to%20the%20second%20momentarily.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20becomes%20even%20more%20evident%20if%20cell%20data%20is%20moved%20from%20one%20workbook%20to%20another.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20Application.ScreenUpdating%20in%20Excel%202010%20does%20exactly%20as%20intended%20and%20locks%20the%20screen%20while%20processes%20such%20as%20those%20described%20run.%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-228931%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-228931%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20David%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20explain%20explicitly%20what%20the%20issue%20is%3F%3C%2FP%3E%3CP%3EI%20use%20Application.ScreenUpdating%20frequently%20in%20my%20VBA%20solutions%2C%20but%20I%20didn't%20notice%20any%20issue%20in%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-715530%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-715530%22%20slang%3D%22en-US%22%3E%3CP%3ETry%20this%20fix%3C%2FP%3E%3CP%3ESet%20the%20ScreenUpdating%20property%20on%20the%20Workbook%20object%20like%20this%3A%3C%2FP%3E%3CPRE%3EWorkbooks(%22your%20workbook%20name.xls%22).Application.ScreenUpdating%20%3D%20False%3CBR%20%2F%3E%3CBR%20%2F%3E%20'%20add%20your%20code%20in%20here%20%3CBR%20%2F%3E%3CBR%20%2F%3EWorkbooks(%22your%20workbook%20name.xls%22).Application.ScreenUpdating%20%3D%20True%20%3C%2FPRE%3E%3CP%3Ewhere%20%22your%20workbook%20name%22%20is%20the%20workbook%20that%20you%20are%20updating.%3C%2FP%3E%3CP%3EI%20posted%20this%20fix%20on%20the%20excel%20suggestion%20forum%20too.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-715552%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-715552%22%20slang%3D%22en-US%22%3ESorry%2C%20I%20realized%20I%20had%20the%20workbook%20(to%20be%20updated)%20minimized%20and%20that's%20why%20it%20worked!%20Try%20this%2C%20although%20there%20might%20be%20better%20code%20to%20minimize%20a%20particular%20workbook%20window%2C%20the%20following%20was%20OK%20for%20me.%20Application.ScreenUpdating%20%3D%20False%20Dim%20wbName%20As%20Window%20Set%20wbName%20%3D%20Windows(%22your%20workbook%20name%22)%20wbName.Visible%20%3D%20False%20'%20other%20code%20here%20Application.ScreenUpdating%20%3D%20True%20wbName.Visible%20%3D%20True%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-715559%22%20slang%3D%22en-US%22%3ERe%3A%20Application.ScreenUpdating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-715559%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F365081%22%20target%3D%22_blank%22%3E%40Elle100%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20didn't%20format%20very%20well%2C%20let%20me%20try%20again.%26nbsp%3B%20Also%2C%20I%20found%20a%20neater%20way%20to%20minimize%20the%20workbook%20being%20updated.%3C%2FP%3E%3CPRE%3EApplication.ScreenUpdating%20%3D%20False%3CBR%20%2F%3EDim%20wbName%20As%20Window%3CBR%20%2F%3ESet%20wbName%20%3D%20Windows(%22name%20of%20workbook%20being%20updated%22)%3CBR%20%2F%3EwbName.WindowState%20%3D%20xlMinimized%3CBR%20%2F%3E%3CBR%20%2F%3E'%20other%20code%20in%20here%3CBR%20%2F%3E%3CBR%20%2F%3EApplication.ScreenUpdating%20%3D%20True%3CBR%20%2F%3EwbName.WindowState%20%3D%20xlMaximized%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
David Griggs
New Contributor

I have seen the other posts on this topic, where the property does not function in Excel 2016, but there still does not appear to be a remedy for this problem.

 

I, like probably thousands of vba writers are now finding their Excel 2010 (or earlier) macros employing this property to suppress screen flicker (and jumping between workbook windows) now make their applications look very amateurish.

 

With so many questions and comments since the release of Excel 2013, when this issue first occurred, there has not been an explanation from Microsoft as to why this property has been disabled and more importantly whether you accept with the level of concern a fix is required.

 

Please can you explain and how users can overcome this issue.

9 Replies

Hi David,

 

Can you explain explicitly what the issue is?

I use Application.ScreenUpdating frequently in my VBA solutions, but I didn't notice any issue in it.

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 article 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?

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 community instead because it's the best place to get support for such an issue.

Someone has reported this problem to Microsoft in the Excel’s suggestion box.

Please check it here and vote for it as I did.

Try this fix

Set the ScreenUpdating property on the Workbook object like this:

Workbooks("your workbook name.xls").Application.ScreenUpdating = False

' add your code in here

Workbooks("your workbook name.xls").Application.ScreenUpdating = True

where "your workbook name" is the workbook that you are updating.

I posted this fix on the excel suggestion forum too.

Sorry, I realized I had the workbook (to be updated) minimized and that's why it worked! Try this, although there might be better code to minimize a particular workbook window, the following was OK for me. Application.ScreenUpdating = False Dim wbName As Window Set wbName = Windows("your workbook name") wbName.Visible = False ' other code here Application.ScreenUpdating = True wbName.Visible = True

@Elle100 

That didn't format very well, let me try again.  Also, I found a neater way to minimize the workbook being updated.

Application.ScreenUpdating = False
Dim wbName As Window
Set wbName = Windows("name of workbook being updated")
wbName.WindowState = xlMinimized

' other code in here

Application.ScreenUpdating = True
wbName.WindowState = xlMaximized