WD98: CreateObject("Word.Application") Fails with Run-time Error

Last reviewed: March 3, 1998
Article ID: Q177097
The information in this article applies to:
  • Microsoft Word 98 Macintosh Edition

SYMPTOMS

When you attempt to create an instance of Word using a Microsoft Visual Basic for Applications statement like the following:

   Set wObj = CreateObject("Word.Application")

you receive the following error message:

   Run-time error '429' -  ActiveX component can't create object.

CAUSE

Using the CreateObject function with an object of type Word.Application or Word.Basic fails if Word is already running.

RESOLUTION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and 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 needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

   http://www.microsoft.com/support/supportnet/refguide/default.asp

To work around this problem, check to see whether Word is already running. If it is not, start a new instance of Word. For example, the following sample procedure uses the GetObject function to create a Word.Application object. If the GetObject function fails, Word is not running, so the CreateObject function is then used to set the Word.Application object.

   Sub RunWord()

      Dim wObj as Word.Application
      On Error Resume Next

      ' Get existing instance of Word if it exists.
      Set wObj = GetObject(, "Word.Application")

      If Err <> 0 then
         ' If GetObject fails, then use CreateObject instead.
         Set wObj = CreateObject("Word.Application")
      End If

      ' Add a new document.
      wObj.Documents.Add

      ' Exit Word.
      wObj.Quit

      ' Clear object memory.
      Set wObj = Nothing

   End Sub

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

For more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q163435
   TITLE     : VBA: Programming Resources for Visual Basic for
               Applications


Additional query words: OFF98 kbcode kbmacro vba
Keywords : kbcode kbprg kbwordvba macword98
Version : MACINTOSH:98
Platform : MACINTOSH
Issue type : kbbug
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.