Click to See Complete Forum and Search --> : Class doesnot support Automation(error 430)
Ali Habib
April 18th, 2001, 08:01 AM
I created ActiveX dll (FormatObject) with one simple class (Format). Then I created another ActiveX dll (Harmonic) with one class (harmCls). This second (Harmonic) dll uses the first dll. Now I tested the second dll by adding a standard EXE project to the second dlls project and making calls to its interface. Every thing works fine. But when I create a new separate exe project and add second dll to its references and make calls to it interface, I get error, Class doesnot support Automation(error 430). And this error occurs where second makes call to first dlls interface functions. Can any one help me in this regard
Thanks
Ali.
Iouri
April 18th, 2001, 08:11 AM
Error 430 - Class doesn't support Automation or doesn't support expected interface
Info: The specified class in the GetObject or CreateObject function call was found, but not exposed a
programmability interface. You can't write code to control an object's behavior unless it has been exposed
for Automation.
Also it might be that one of you dll files on that machine is out of date. Error 430 usually occurs when you have
a version of a dll that does have the same version of an interface that VB is looking for. What you should do
is make sure you are replacing all files in the installation routine by version. NOTE if you are using
VB package and deployment wizard it will not replace com dll's no matter what, the best bet here is
to rename the file that you want replaced and then run the installation.
Iouri Boutchkine
iouri@hotsheet.com
codeguru.com
Copyright Internet.com Inc., All Rights Reserved.