VBA – Scrrenupdating….does .View take precedence (Env: O2000 sr-1 on eit

Topic

New Reply

Hi,

Would anyone know if it is so, that if I change the .View setting in word this overrules any
application.screenupdating=false that may precede it ??

(it definitely looks so, eg. I swap from “PageView” to “HeaderFooterView” and back, my screen is constantly
updated with a lot of flickering, though Application.Screenupdating=False)

Any ideas – thanks,
;o)) henrik

Reply | Quote

Replies

In general, setting ScreenUpdating = False in Word and Excel, or Echo = False in Access, works only partly; it doesn’t seem to prevent flickering. I have noticed this in many situations.

Reply | Quote

Screenupdating = False gets overridden by Word in lots of circumstances.
Short of using the Windows API to lock the window, there’s no geberal solution.

Often one can re-organize/re-code the code to reduce screen flicker.
In Word, the best way is to use the Range object instead of the Selection object.
Once the Range object is used, one needs to re-organize the code to reduce flicker.

If the code was originally written for (or designed AS IF), say, Word 97, screen flicker will be exacerbared in Word 2000 and Word 2002, unless the code is redesigned to take into account the difference between MDI on Word 97 and SDI in Word 2000/2002.

Reply | Quote

Howard, appreciate your comment, thanks.

What API would you use ?
– wouldn’t it block for other dialogs from the same application, or would they run in separate threads ?

;o) Henrik

Reply | Quote

I would not use the API.
Best to convert from Selection to Range object, etc.

You’ll end up with much faster and easier to maintain code.

Reply | Quote

Is it possible to minimize the flickering window(s) while the process runs?

Reply | Quote

To some extend – if I following a view change add a .screenupdating=false, then it works (most the time) until the next change in the “View” setting.

Reply | Quote