That is a good idea that I have used already, and it saved me a lot
of debugging time. The problem is when the error is not coming from
your app, but from a component that your app is calling. In this
case, you get "Cannot connect to ComponentA", but it is really
ComponentB that cannot be created by ComponentA.

BTW You do early bind with CreateObject only if the target is defined
as Object. I use it when I have to connect to a remote computer
(selected by the user, thus I cannot use dcomcnfg) or when I dynamically
load a component from its guid.

Marco


-----Original Message-----
From: Randy Cornish [mailto:rlcornish@c...]
Sent: Tuesday, July 30, 2002 6:51 PM
To: professional vb
Subject: [pro_vb] RE: Error Code 429


To piggy-back off of this, what I often do is create a small "test" 
applet that uses an approach similar to that below.  The difference is 
that if you early bind in your production app (a good idea), you may not 
be using CreateObject(0.

Create a small VB app with one button, "Test Environment".  Mail it to 
the user and all it does is try to instantiate each ActiveX OCX/EXE/DLL 
that your app uses.  It might take a while to dig all that out of the 
VBP, but you only need to do it once.  The app tests each reference and 
if any of them fail, puts up a helpful MsgBox.  There are other, more 
sophisticated ways to do this, but this is the easiest to describe in a 
short reply.

R