Hide screen updating excel

27-Oct-2019 04:18

I would like the queries to be invisible while they are running, but currently the user sees 50 query windows open/close which is ugly.

Is there a way to automatically minimize/hide query windows or disable screen update?

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.

hide screen updating excel-41hide screen updating excel-61hide screen updating excel-56hide screen updating excel-17

Here is an example from a Visual Basic client: In the above example, Word launches but does not appear anywhere on the screen. (It does, though, show up in NT's Task Manager, in its list of running processes.) Despite this apparent lack of response, Word is very active and quite capable of doing everything it is told-creating a new document, inserting the message, , saving the file, closing it, and quitting.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.EXE process.) How much of a difference does invisibility make?So, I prefer Open Query action rather than Run SQL action.Regards, jon [font=Verdana][size=2]You should not have to do all that.

Here is an example from a Visual Basic client: In the above example, Word launches but does not appear anywhere on the screen. (It does, though, show up in NT's Task Manager, in its list of running processes.) Despite this apparent lack of response, Word is very active and quite capable of doing everything it is told-creating a new document, inserting the message, , saving the file, closing it, and quitting.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.EXE process.) How much of a difference does invisibility make?So, I prefer Open Query action rather than Run SQL action.Regards, jon [font=Verdana][size=2]You should not have to do all that.Everyone I have talked to has advised me to avoid using macros when possible.