XL: Error Creating OLE Automation Object with Microsoft Excel

Last reviewed: September 2, 1997
Article ID: Q129252
The information in this article applies to:
  • Microsoft Excel for Windows 95, version 7.0
  • Microsoft Excel 97 for Windows

SYMPTOMS

When you use the CreateObject function or the GetObject function in a procedure to create or return a Microsoft Excel OLE Automation object, you may receive one of the following error messages.

In Microsoft Excel 97:

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

In Microsoft Excel version 7.0:

   Run-time error '499':
   User-defined error

In Microsoft Excel version 5.0:

   Run-time error '440':
   OLE Automation error

CAUSE

This behavior occurs if you use an incorrect value for the class argument of the CreateObject or GetObject function. The class argument consists of the name of the application providing the object (appname) followed by a period and the type of class of object to create or return (objecttype).

The application names "Excel.Application" or "Excel.Application.5" may be used for Microsoft Excel versions 5.0 and 7.0. However, only the application name "Excel.Application" may be used for Microsoft Excel 97.

Because of this, you will receive an error message when you run any of the following commands in a procedure in Microsoft Excel or Microsoft Visual Basic:

   Set myApp = CreateObject("Excel7.Application")

   Set myApp = GetObject(,"Excel7.Application")

   Set myApp = CreateObject("Excel.Application.7")

   Set myApp = GetObject(,"Excel.Application.7")

RESOLUTION

Microsoft provides examples of Visual Basic for Applications procedures 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. The Visual Basic procedures in this article are provided 'as is' and Microsoft does not guarantee that they can be used in all situations. While Microsoft support engineers can help explain the functionality of a particular macro, they will not modify these examples to provide added functionality, nor will they help you construct macros to meet your specific needs. If you have limited programming experience, you may want to consult one of the Microsoft Solution Providers. Solution Providers offer a wide range of fee-based services, including creating custom macros. For more information about Microsoft Solution Providers, call Microsoft Customer Information Service at (800) 426-9400.

To avoid receiving an error message when you create or return a Microsoft Excel OLE Automation object, use any of the following commands:

   Set myApp = CreateObject("Excel.Application")

   Set myApp = GetObject(,"Excel.Application")

   Set myApp = CreateObject("Excel.Application.5")

   Set myApp = GetObject(,"Excel.Application.5")

For compatibility between all of the versions of Microsoft Excel listed above, it is recommended that you use the application name "Excel.Application" rather than "Excel.Application.5".


Additional query words: 7.00 8.00 XL97
Keywords : AutoGnrl kbcode kberrmsg kbinterop kbprg
Version : 7.00 97
Platform : WINDOWS


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: September 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.