Use the built-in Help that comes with Excel/Access 2. A lot of VBA code can be acquired by using the Macro Recorder. I'm seeing a lot of posts about issues with Excel 2013 repainting the screen after running a macro but I have not seen a clear resolution to what I have been experiencing.I have an existing workbook (which worked perfectly fine in 2010) and in the main sheet of the workbook there is an index of existing sheets for the user to select. If I switch from Excel to say Outlook and then return to Excel the selected sheet is repainted correctly.
Note code snippets posted are just that and do not include error handling that is required in real world applications, but avoid On Error Resume Next The more I read about issues with the releases since Office 2007, I am glad that I have no real reason to upgrade.
My favorite was about Excel 2010 and outdated color printer drivers where having the the supposedly outdated printer selected as the default printer causes constant screen refreshes, flickering and other issues.
- still, I have that flickering with excel 2013-W8 and not with excel 2010-W7 since the main sub (and those called by it) has to open all those many workbooks, for reading data inside them, I'm starting to think flickering is due to this.
but with no idea of why should that happen with excel 2013-W8 only.
To follow up on Pete and DS, why are you switching between workbooks? Screenupdating=false won't prevent the "switching" from being displayed, so I'm not understanding why you wouldn't see that in 2010 as well.
To follow up on Pete and DS, why are you switching between workbooks? Screenupdating=false won't prevent the "switching" from being displayed, so I'm not understanding why you wouldn't see that in 2010 as well.starting from your kind last three posts I checked more thoroughly my code and can state what follows: - I do have "activate" stuff but it resides in subs only with the specific task of taking the user around many open workbooks (rather than having him select them through taskmanager, or alt tab or via the window bottom toolbar) while the main sub (and those called by it), which is called for processing data in all open workbooks, does not make use of any "activate" method at all - my guess about switching between workbooks being the flickering cause was just a guess that turned out to be wrong.Has anyone experienced this before and found a solution?Hello, The beginning of t he code I am writing turns off screen updating, but the screen still updates as the code runs. The last statement of the procedure sets Application. Now if I remove the Screen Updating statements from the code then the sheet is displayed correctly and usually in a short period of time.So from my viewpoint Screen Updating is not working correctly.well that's both reassuring and frustrating at the same time.