When it "gets too busy" it does not update the screen anymore (done simply with = "any text") and it does not respond to user input in any text box. Is there a way I can get the program to do screen update and respond to user input while it is busy? So UI runs in the main thread and all additional calculations are running in a separate thread.When you do all-in-one thread - this leads to delays for processing UI related codeactually I started to use the worker class to then realize there is a refresh() method for text fields. I fortunately found it in the context of learning about the Background Worker You'll probably need to move the heavy calculation and communication to a separate thread.The functionality depends on Word, not on the Automation client.But it also works even if you run your Automation code from Word itself.
Screen Updating = False If my Debug = False Then On Error Go To Error Handler I'm afraid that's pretty much it. Screen Updating End Sub As I step through the code when I hove over Application.screen Updating it always says True. Then put it in debug mode and step through with screen updating turned off again, you should find that you still see the numbers going in one by one.You can verify this by launching Word the old-fashioned way and opening File1 at the bottom of the File menu after running the sample code.Although it would be difficult to do an exhaustive test, in theory this should work from any Automation client-Visual Basic, Excel, Power Point, or any other.First off, you can set property; assuming that the range of cells and the array of values have corresponding dimensions.The ways discussed above were tested in the template[d] code below.