Error 430. Not resolved

Hi All,

My problem is error 430 "Class does not support automation". I have read all the previous responses on this and other forums including vbkb Q193172 which is addressed to VB6, unfortunately they have not helped me.

My app is VB5. It installs OK on Win98/95/Me. The Me PC and laptop 95 have VB installed.

I added some code behind the OK button on form welcome in setup1. The code searches for the app.exe, deletes the files if found in the dir and then Rm the dir before installation begins.

With this added code it will install ok on WinME and laptop95 PC's.

On the 98 PC I get the error when I click ok on the welcome form, this is where the search starts.

It's obvious that the search code is causing the trouble, I believe the 98 PC is missing DLL which the other computers have but I do not have a clue which one or how to install them from an installation disk.

From a suggestion from this forum I installed a newer version of MDAC on the 98 PC, unfortunaltely it made no difference.

Any help appreciated.

Regards,

Alan.

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 replaceing 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.


If nothing helps then try to install VB on the user computer and check if the error disappeared.



Iouri Boutchkine
[email protected]

Hi Iouri,

Thanks for the response, it has prompted me.

First the bad PC had the wrong date format which I fixed up.

I checked the app DLL dates and found ten to be out of date on the PC causing trouble with the error. I can rename each one and replace it with my app version, one at a time to see which one is causing the error when I search for a file before installation begins.

If I distribute this app on a CD, its possible that it will not work because of DLL dates. If I could remove the existing DLL's before I install from the CD then other apps on that PC may not work.

I am using FSO to search for the file, is there another method to find a file that may not cause this error?

Thanks again for your help.

Regards,

Alan.