> I'm using the VB5 setup whizzer on a project wherein the
> .VBP file references msado15.dll.

> This file shows up in all windows of the Setup Whizzer
> EXCEPT the list of files to be included in the installation.
> If I create the setup disks, it is also not included there.

> Is this a known problem?  Is this a problem?

> Thanks for any info.
> Regards,
> Joe

> This file is part of MDAC (ADO etc). It should be installed by
> MDAC_TYP.EXE (the MDAC setup), which should have been automatically
> included by the wizard.

> BE VERY CAREFUL HERE:
> The wizard picks up MDAC_TYP.EXE from a specific folder (on my machine
> it's C:\Program Files\Microsoft Visual
> Studio\VB98\Wizards\PDWizard\Redist). It doesn't care what version of
> MDAC you have installed on your machine, or which version you have
> referenced in your project. It just says "Ah, MDAC is required so I
> need to include MDAC_TYP.EXE and I know where I keep that". Make sure
> you've got the right version in that folder. If you get it wrong the
> install goes fine but, when they try to run your app, they get the
> helpful error message 429 - "ActiveX component could not create
> object".

> > Dear Folks:

> > I'm using the VB5 setup whizzer on a project wherein the
> > .VBP file references msado15.dll.

> > This file shows up in all windows of the Setup Whizzer
> > EXCEPT the list of files to be included in the installation.
> > If I create the setup disks, it is also not included there.

> > Is this a known problem?  Is this a problem?

> > Thanks for any info.
> > Regards,
> > Joe

> Method (~) of Object(~) failed.

> I've had that when I've referenced a newer MDAC and (accidentally)
> ditributed an older and the target system had an even older version
> than what I distributed.

> For instance...

> Target system has 2.1
> I've distributed 2.5
> I've referenced 2.6

> And gee... COM was supposed to fix all this!!! :)