err # 430

Hi,
After converting vb system to EXE , I get an err saying
"Class does not support automation or does not support expected interface"

What will be the problem.

Can anyone help in this.



ThankU
R.Priya.

Using ado 2.5 or 2.6?

seems to me that one of the dll's or ocx's u use has to be recompiled....

I don't get this err. if i compile the system from where i want to acces the exe. I get this err. only if compile the system in one place and run it in another place.


I use DAO 3.6, ADO2.1, & microsoft scripting runtime.


ThankU
R.Priya.

do u have any "self made" dll's or ocx's in this project?

I did have the same problem once, this is the auestion and the answer i got here:

Question:

When i ditribute my application, i get the folowwing error when i want to open it: ERROR NR 430: CLASS DOES NOT SUPPORT AUTOMATION OR DOES NOT SUPPORT EXPECTED INTERFACE.

I used a ADO 2.6 reference in my project to work with XML thru ADO.
Terefor the installation program installs MDAC 2.1

On the machine i developed the application it all works fine?

Someone knows a solution for this ???


Answer: (provided by crispin)

d/l and install MDAC 2.6, you can get it from www.microsoft.com/data

then replace the one that the P&D wizard uses by default in the

C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist

End Answer

I do not know if this helps you in any way, but you have to search in this direction, i think.

The reason for the error was that there were conflicts between the recordset class between several versions of ADO.

Greetz, Luc

Quote:

---

Originally posted by spriya
Hi,
After converting vb system to EXE , I get an err saying
"Class does not support automation or does not support expected interface"

What will be the problem.

Can anyone help in this.



ThankU
R.Priya.

---

Whenever you distribute your application, i.e. install it on a computer other than one on which it was developed, you have to make sure that all the OCX and DLL files used in the application have been copied and registered correctly on the client machine. If one of the components has not been copied/registered correctly, the above error can occur.

To avoid this, you can use either the Package and Deployment Wizard shipped with VB or any other tools such as Inno Setup, GKSetup, Wise Installation, InstallShield etc. to create a distributable package from your project. Such a package will usually take care of copying and registering all the other DLL and OCX files on the client machine.

.