WD2000: Shell Command Does Not Start Second Instance of Word (209910)
The information in this article applies to:
This article was previously published under Q209910 SYMPTOMS
When you use the Visual Basic for Applications Shell function to run Word, another instance of Word is not created if Word is currently running. In versions of Word prior to Word 2000, another instance of Word is run when you use the Shell function.
CAUSE
This behavior is by design as part of the Word 2000 Single Document Interface (SDI).
RESOLUTIONMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
Adding any Word command-line switch to the command line will run a new, separate instance of Word. However, Word has added a new command-line switch, "/w", to enable you to run a separate instance of Word. Using this new command-line switch opens a new, separate instance of Word with a blank document.
For example:
Shell "C:\Program Files\Microsoft Office\Office\Winword.exe /w"
MORE INFORMATION
For more information about command-line switches, click Microsoft
Word Help on the Help menu, type "startup" in the Office Assistant or the Answer Wizard, and then click
Search to view "Control what happens when you start Microsoft Word".
Modification Type: | Major | Last Reviewed: | 6/17/2005 |
---|
Keywords: | kbbug kbnofix KB209910 |
---|
|