How To Dismiss a Dialog Box Displayed by an Office Application with Visual Basic?

[jhon]

Hi friends,
I am facing some difficulties while dismissing the dialog box that is displayed by an applications of Microsoft Office. I am trying to dismiss that by using the Visual Basic. When I am automating an Office application in VB it displays a dialog box. The dialog makes it appear that the Visual Basic stops responding because Visual Basic is expected to dismiss the dialog. So help me to fix this issue.!! Please tell me how to dismiss a Dialog Box displayed by an Office Application with Visual Basic.??

[HellBoy21]

Sometimes, you may want to automate an Office application but that does not require any user interaction with it. In this case, if the Office application displays a dialog box appears that the application stops responding until a user can dismiss the dialog. However, you may not have any user sitting at the computer to dismiss the dialog. Office applications were not designed to run unattended. Therefore, an application that automates Office can sometimes be a dialog box that has shown the Office application. Thanks to the usual tests of the application, you can usually determine which dialog boxes appear and write code to avoid them.

[Bigga Lexx]

You can use the described strategy to prevent displaying any dialog boxes to automate an Office application. Determine if the property or method you are using (which is causing the dialog box) has optional arguments that can happen. Sometimes, you can avoid a dialog box passing all arguments to the property or method. For example, if you use the Open method to open an Excel workbook and that book is protected by a password, Excel displays a dialog box that prompts the user for the password, if not provided the password argument when calling the Open method. To avoid the dialog box, provide a value for the Password argument when calling the Open method. Similarly, when using the Close method to close a document, it is often helpful to specify the SaveChanges argument to avoid a dialog appears asking the user to save the changes.

[Rob Dizzle]

Study the object model of the Office application to see if there may be some property that prevents certain dialog boxes. For example, the Excel Application object has properties AskToUpdateLinks and AlertBeforeOverwriting. Set the property Application.DisplayAlerts (Excel, Project, Word) or use Application.DoCmd.SetWarnings False (only in Access) to turn off warning messages. Most of the dialog boxes can be avoided with this configuration, but not all.

[DANIEL 602]

You can also try the method described by me for dismissing the dialog box. Use the On Error statement to avoid error messages at runtime which might arise, for example when trying to establish when there Application.ActivePrinter no printer driver installed on the user's system. Test the application thoroughly to help anticipate when dialog boxes may appear. For example, suppose you call the SaveAs method of an Office application to save a file. If that file already exists, you may receive a dialog box asking for confirmation to replace the existing file. If you modify the code to check the file before calling the SaveAs method, you can avoid the possibility of dialog box appears. For example, if the file already exists, delete it using the Kill statement before calling the SaveAs method.

[Soumen]

I am explaining you the logic of the dismissing a Dialog Box displayed by an Office Application with Visual Basic. The Automation client calls the method PrintOut Word Document object. If the user's default printer is configured to print to the FILE port, a call to PrintOut generates a dialog box that prompts the user to type a file name. To determine if the PrintOut method causes this dialog box appears, the automation client Visual Basic uses a Timer control to detect idle time after calling the PrintOut method. Before calling PrintOut, Timer is enabled and set to break out in five seconds. When PrintOut completes, Timer is disabled. Therefore, if the PrintOut method completes within five seconds, the Timer event never occurs and there is no other action. The document is printed and the code execution continues beyond the PrintOut method. However, if the Timer event occurs within the five-second interval, it is assumed that the PrintOut method has not been completed and that the delay is due to a dialog that waits for user input data. When the Timer event occurs, the Automation client gives focus to Word and uses SendKeys to dismiss the dialog.