Well, the function is quite long, but you're looking at the function's entry point. The immediate window says True, then False, then True again as expected, but the code doesn't seem to have any effect on the application. If all of this happens, then you know it is working correctly. Net 2003 and Office 2010 Code: Excel Graphing | Excel Timer | Excel Tips and Tricks | Add controls in Office | Data tables in Excel | Gaussian random number distribution (VB6/VBA, VB.
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.
Article contributed by Daryl Lucas Many people know they can speed execution of Word Automation by turning off screen updating: Word. Screen Updating = False Many do not know, however, that they can get an even greater speed boost by hiding the application altogether.
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.
I started to debug, and immediately after the "Screen Updating = false" line executes, I go to the immediate window and type: Debug. Any clues on how to solve it would be greatly appreciated. Screen Updating = True End Sub _________________________________________________________ Private Sub Check_for_Open_Workbook() Application.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?An approach to take in these types of situation is to start a new thread with computation intensive (or potentially blocking operation such as I/O) processing in a separate thread, allowing the GUI to stay alive on the main thread.Microsoft seems to have an introduction to multithreaded applications in Visual Basic, using the facilities provided in the .