In the above code, you could omit the lines that create and use the Word.Application object and replace them with invisibility lines: Notice that you want to put the Word. Visible = True line in an error-handler or in a spot where you know it will be run if something goes awry. (If you do get stuck with an invisible Word in the middle of a crash, you can launch the Task Manager and kill the WINWORD.Either way, you use code to turn the warnings off, perform the set of tasks, and then turn the warnings back on.You attach the code to an event, such as the Click Event of a command button or the Open Event of a form.Important: If you use this setting to turn action query confirmation messages off, Access will not display the messages on that computer even for a database that contains a macro or module that turns the messages on.There are two basic ways to turn action query confirmation messages off for a set of tasks: by using a macro, and by using a VBA module. Here is a pic of the status bar while the macro is running.
If you have turned off screen updating using the line Application.
That's about 1 second for every 7-not a trivial amount if your job runs longer than that. Chief among them is that repagination routines don't work when Word is invisible.
If you need to update page numbers, you will have to show the application window before doing the update: With See Page X of Y displays or prints as Page 1 of 1, Page 2 of 2 etc. I hear rumors that you may also need to work with the Range object instead of the Selection object, but I have not tested this nearly enough to give a list because I do almost all of my work with Ranges.
You attach a module to an event, and when the event occurs, the module runs.
For example, you might attach a module to the On Open event for a form. The following procedure explains how to use the Do Cmd.