Screen updating translate Pantyhose video chat

I'm now going to take a step back and look at everything, de-constuct and rebuild...

Should be fun :question: Thanks again for your help.

I was hoping you would be able to help me (once again) I know the code that stops a screen updating when a macro runs... My code is designed to create a document made up of various statements that are housed in different word templates. But it's a bit of a long process (not to take away from the excellent specifics Paul is giving).

Screen Updating = True ..it doesn't seem to be working effectively in my current project. There is a lot of material there which will help you translate from recorded macros/heavy use of the Selection object to a slicker program.

'My code' based on the users selection will open the relevant word template, copy its content, close it, then paste it into the original document. Sorry for the long-winded explanation, but you said one of the reasons why you used the old code was because you understood it.

Is there anything that I can add to my code that might eliminate the updating? Would it help it the above was placed in the template that is being opened ? Screen Updating controls the updating of the current document's window, but not the updating that occurs when documents are opened/closed. If your screen "locks up" because of an effective use of the Application.

Also, if you are opening multiple documents without user interaction, you might try opening them with the optional Visible argument set to false. However, in my experience, asking this question generally means (with respect), that you would probably benefit from a revamp of your code, rather than bracketing all your subroutines with some way of hiding your actual processing. However, in my experience, asking this question generally means (with respect), that you would probably benefit from a revamp of your code, rather than bracketing all your subroutines with some way of hiding your actual processing. Screen Updating = True' in a called subroutine invariably means you're causing the screen to flicker at that point if any ranges before the end of the visible range have been expanded/contracted or anything on screen has had its formatting changed. Below is an example of the code I am using, sorry, for security reasons I can't put in the actual code, but this is the basics. With the code you posted, that was certainly the case.

Thanks everyone for your feedback and help on this so far. If anyone could help streamline this code that would be great. And, IMHO relying on flickering for a progress indicator is poor practice - the showing something meaningful on Word's status bar or a proper progress bar is far more preferable.

I have little experience of VBA and what I have put together comes from information obtained online. As for using the Insert File method: Dim Str Var As String If Opt1 = True Then Str Var = "" If Opt2 = True Then Str Var = "2" If Opt3 = True Then Str Var = "3" If Opt4 = True Then Str Var = "4" With Active Document. Insert File File Name:="E:\MYDOCUMENT" & Str Var & ".dot", _ Range:=. Range, Link:=False End With I disagree that we disagree, Paul. Let me clarify my point: it was not that screen-flickering was good practice, but that the next step into making it work "correctly" might not necessarily be worth the time-investment/learning-curve...

Dim str VARIABLE1 As String If Opt1 = True Then str VARIABLE1 = Word. especially if the OP gets to the point where so many documents are being opened/closed in the background that the screen is actually frozen for a noticeably long time.

Leave a Reply