Article ID: 129252 - View products that this article applies to.
This article was previously published under Q129252
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:
In Microsoft Excel version 7.0:
Run-time error '429':
ActiveX component can't create object
In Microsoft Excel version 5.0:
Run-time error '499':
Run-time error '440':
OLE Automation error
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:
Microsoft 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. To avoid receiving an error message when you create or return a Microsoft Excel OLE Automation object, use any of the following commands:
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".
Article ID: 129252 - Last Review: October 11, 2006 - Revision: 2.3
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.