Runtime error '429' - ActiveX component cant create object

I need to install an application which has been written and compiled in VB5, and has been packaged in to 4 setup disks (ages ago).

It seems to install OK on one machine, but when I run it it says:

"runtime error '429' - ActiveX component cant create object"

Presumbably it is having problems registering a .dll but there are at least 10 of them (one a class that contains user written code, and the rest being standard VB type JET DAO things).

Also when I try and install the app on a different PC it cant cos it cant access a file (that is clearly there and has full access!)

Do I need to try and create a new version of the package and deployment caboodle again?

thanks
Kester

Make a new setup and make sure that the setup disks aren't damaged.

I should have pointed out that the setup disks that were initially created, are on a network so presumably are not physically damaged!

Also I did try packaging it again (after I got hold of VB5) but it still only runs on my PC (the one I compiled it on) and installs, but fails when run with above same error on all other machines.

It must be due to some problem with the compiled class .dll file or others that are maybe missing on others PCs?

Make sure that all of the DLLs that the program needs are being included in the setup. P&D Wizard doesn't always find them.

thnx for quick reply and suggestion!

how does one know all the .dll's that one needs? The main .vbg consists of 2 .vbp's that compile to an .exe and an .dll.

P&D grabs loads of others such as jet35dao.dll etc.

Is it possible that it will only run on PCs that have VB5 environment installed and not on others. if so which files could it also need?!

thanks
Kester

Go to each project; go to the project menu, and select references. Highlight each checked item in the dialog box, and write down the names of the DLLs that are associated with the projects' references. Make sure you do this for both projects! The list is all the DLLs you should need.

I think that has solved it!! I found the file it wasn't grabbing and manually added it.

thank you ever so much, as I was really getting desperate!

kester

It could be a versioning issue. To ensure it isn't

(i) Set Binary Compatibility
(ii) Ensure all objects are created with CreateObject, rather than using the New keyword