>What I recommend that VFP6 developers do if at all possible is to avoid using our Setup Wizard to install any ODBC drivers, but rather include the separate MDAC_TYP.EXE installer that ships with Visual Studio 98 (install VB) or from http://www.microsoft.com/data/.
>
>The Microsoft Data Access Components is a more complete set of data related components you might need for your application, especially 3-tier ones. It contains all ODBC drivers, OLE DB providers, ADO, and RDS components. Its included in the REDIST.TXT file so you can distribute it with your applications. Additionally, its easier to pick up an updated version from the above web site. I'm sure someone around here like Ed Rauh could show you how to use Windows Scripting to combine the two setups.
>

I'll go one better than that - if you'll confirm that we can distribute DCOM98.EXE from the Visual Studio CD by Thursday evening, the early part of next week I'll post two things; one will be a script for execution under WSCRIPT to handle installing DCOM for 95 and 98 silently without forcing a reboot, and will leave a crumb that a post-Setup executable could examine to trigger a reboot. This will be dependent on the scripting host already being installed on the system. It'll be the responsibility of the post-Setup executable to reboot as needed.

The other thing I can do is a tiny brain-dead simple wrapper that is fired in place of Setup Wizard's SETUP.EXE; it'll check for DCOM, install DCOM if it's appropriate and available (it'll look in a standard location relative to the wrapper) silently, recording the need for a reboot, launch and wait on Setup Wizard to complete, passing along any command line parameters, and then reboot if necessary. It won't be terribly flexible, but it will drop in on top of a standard NETSETUP directory and do its thing, without the need for the scripting host to be present. Just add the wrapper and DCOM98.EXE to the distribution.

If somebody else wants to code the C wrapper, I can post pseudocode for what has to be done, what API calls need to be made, etc.

OK?

>As for DCOM files, it does not appear in REDIST.TXT, so I don't think you would be able to distribute it. Generally, we don't include system updates with our setup wizard.
>
>>Randy:
>>
>>Any hope of getting the DCOM95/98 installed on our development computer to be included (like the ODBC drivers are) in the setup CAB or additional file so our users can install it (if needed) first if the SETUP does not detect it?
>>
>>Thanks.
>>