Run-Time Error 429

[gbernhard]

I have a VB application I'm trying to deploy, however, on some PCs I'm getting a run-time error 429. In this application I have some class modules I've created (not saved as DLL but as CLS). Could these modules be causing the error and why on some PCs and not others? How can I correct this problem? This application will run until I open a form that sets my classes and sets an ADO connection. Normally if there is a problem with the ADO I have an error message that says "Connection can't be made.". On the PCs that give me 429 I don't even get the form. The form makes the connection and set the objects on load. Please, Please help I'm at my wits end.

[Jop]

Did you include all the used OCX and DLL files in the installer?
If not, maybe that's the problem

[jtm7699]

I know that when I wrote a program using the Winsock control, the first time I accessed the control on a WIN98 machine, after opening the program, I would get and error message. The next time it would be fine. I found that if I put in an "On Error goto Whatever" and had a check for that error number, I could tell it to resume next on that error and everything would work fine.

Try something like that

[gbernhard]

Thank you for the reply. Yes, I've included all known OCX and DLLs associated with the application. The application will load (Switchboard), it's when I try to activate the form that sets all of the connections and objects. Do I have to register CLS modules as well and why on some PCs does it work and others not? Is ADO possibly giving me problems and how do I ensure those DLLs are registered?

[StillAwake]

Not sure if this will help.
I had a similar problem. It turned out to be registry settings for dao350.dll

HOWTO Insuring Jet 3_5 Is Installed Correctly (Part I)
http://support.microsoft.com/support.../Q240/3/77.ASP

[Glenn]

If your class modules are included as part of your EXE (not in a DLL) you do NOT have to register them. The fact that your app loads, typically means that the OCX's are register correctly. The problem is that DLLs don't load until they are required. Its sounds like its an ADO problem. What version of ADO are you using. Get a copy of the MDAC from the Microsoft's data http://www.microsoft.com/data/ web site and install on the client PC's first.

I started doing this when I switched to ADO, that way I did'nt have to add MDAC to all my installations.

Hope this helps