I have created a VB 6.0 application which connects to a SQL Server 6.5
database using ADO.  I plan on deploying it as an Active X control over our
Intranet.  The problem, is that it only works on computers which already
have VB installed, or where I have gone to the microsoft web site to
download ADO 2.0.

I am wondering how to handle getting the ADO 2.0 control installed to 120
people's PCs.  How could I have my VB application (or html) look for this
object being registered and automatically install it for those who don't
have it.  I have tried including the ADO control into the .cab file I built,
but it didn't seem to work.  I keep getting a "429 - Unable to create
object" error.

Also, will ADO 2.0{*filter*}up PCs currently using ADO 1.5?

Any help would be greatly appreciated, as I have two weeks to get my VB
application rolled out to everyone.

Thanks, Brian Butzine

First make sure they have the appropriate DCOM installed then install mdac
2.0 then install your app.  I to found that the MDAC the MS provides with
VB6 does not install properly when bundled within the cab, never did find
out why.  Try Dl'ing the one from the MS site and install it seperately.

If you have SMS then use it to push everything.  You could also wrap both
installs inside the install of the Install Shield package as I know our IS
department has done this before.  If you are going over an Intranet then set
up the MDAC 2.0 cab from MS on as seperate install, installing both DCOM and
MDAC if the machines don't already have it.  You should be able to write
some small VB or Java app to test for it.

As for 1.5 vs. 2.0 don't have the slightest.  Shouldn't but those words
don't necessarilt mean a lot thses days.