Class does not support Automation Error

[Anitha B]

Hi,

When I compile and create an executable for my application and place the executable in my server, I amnot able to use the same executable in another system. I get an error message "Class does not support Automation or Expected Interface".

Can anyone help me with resolving this issue?

Thanks,
Anitha

[DSJ]

Usually this is because a DLL or control referenced by your project is either not registered on the new PC or it is, but is not the correct (or a compatible) version of the DLL or control.

[Iouri]

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.



I got this error on the line Set rs = New ADODB.Recordset on the user machine. (i did not have this
error on the machine where VB installed and I had the development done)
I installed VB on the user machine and the error dissappeared. After I uninstalled VB problem did not
come back



Iouri Boutchkine
iouri@hotsheet.com