Printable View
Hello everybody.
I am developing a user interface using Control Arrays. I built the setup procedure with the Package & Deployment Wizard, and then I installed it in a computer without VB. When I run my program, the 430 Error occurred.
It seems to me that this error was generated by the Control Array. Is there anybody who can confirm that Contol Array can arouse this error? And how can I avoid it?
Thank you.
riccardo
I don't think this has got anything to do with a control array. err 430 is 'class does not support automation, or does not support expected interface'. This is typical COM error. Are you using any objects in your code (like custum created classes, or are you linking to other applications via com (like Word or so).
This can also be caused by an incorrect version of a dll. Eg, you are createing an ADO recordset version 2.6, and the client computer only has ADO 2.1.
Tom Cannaerts
[email protected]
Programming today is a race between software engineers striving to build bigger and better idot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning -- Rich Cook
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
[email protected]