Run-Time Error '430'

I have an .exe that works fine in 2000 but when I try and run it on a 98 machine (not second edition) I get the following Run-Time Error.

Run-Time Error '430'
Class does not support Automation or does not support expected interface

I have checked my refs. and all seem to be present except for VB6.olb.

Does anyone know what this file is used for.

I am using the FileSystemObject but scrrun.dll is present on the 98 machine.

Any help would be greatly appreciated.

Thanks,
Derrick

I would strongly suggest compiling the exe on a 98 machine.
If you are not going to use a setup package then this is your best option. Even if the dll's exist on 98 often they are older versions and are not compatible. (I luv programming with COM)

I guess this might be obvious but I dealt with this a little while ago with crystal reports and the RDC.
Once I compiled on 98 I have had no problems.
Give it a try

I would strongly suggest compiling the exe on a 98 machine.

That's the strangest advice I heard for weeks!

I you want to run a VB on whatever Windows machine other then your own development machine you should create a setup package first and install it on the target machine.
You can use the Package & Deployment Wizard (which comes with VB) for this or use the free INNO setup from www.jrsoftware.org

Arnout V

I am pretty sure that it is not strange advice. but correct me if I am wrong

The app that I just finished was to be created using only the existing DLL's on the client machine.
i.e avoiding using the setup wizard and overwriitng the existing DLl's. Because my app is to be deployed on several thousand machines i was told (and agreed) that it would be less hazordous to not installl or upgrade any new DLL's .
Other VB applications already on these machines rely on these DLL's and the thought was that replacing them with newer versions could cause problems with other applications.
besides registering the same named DLL twice???
is bad n'est-ce pas??

isnt this kinda like the MDAC issues??

Anyways I received an error very similar to this a week and a half ago and when i compiled the app on a 98 machine as opposed to my 2000 it solved a crystal report DLL error.

I hope I havent misled, but i think that this is wise

I have the same problem with you. If you found any solutions please notify me!

But with me it is a little more strange. I am trying to rum my Application in Windows NT and I built it in Windows 2000! It should RUN!

Tahnk you!

It's almost certainly a .dll or other dependency problem. As ArnoutV said, the best way to address it is by creating an installation package. If you're worried about overwriting critical files, then install your dependency files into the app directory, rather than into the Windows system directory.

Mine was caused by having the wrong version of scrrun.dll on the 98 machine. What I did to find this out was looked at my refrences and wrote down all the filenames. One by one I did a search on my developement machine and test 98 machine until I found my problem. This will probably work for you as well. It is a bit time consuming but I learned a great deal on references. Even though NT and 2000 are very similar you can still get this problem. If you are using any references to Microsoft Office start with those. Hope this helps,
Derrick