Very Computer

> check the ms site at www.microsoft.com/ODBC/
> and it will take you to the MDAC pages.
> as I understand it MDAC is Microsoft Data ACcess ...

> the self installing exe has a bunch of stuff for ODBC, RDO, ADO etc...

> > Does anyone know if there is a Windows Installer Merge Module available
to
> > install the ODBC components? There should be, after all, they're both
> > Microsoft technology.

> > Thanks for your help.
> > Jim Walsh

> Q192009 : HOWTO: Invoke Silent MDAC or DA SDK 2.0 Redistribution
> Q177913 : HOWTO: Use the MDAC Standalone Setup EXE in Unattended Mode

> These apply to both the mdac_typ.exe and mdacfull.exe
> redistributables. If you want to avoid any licensing issues
> you really should use the official distributions even though
> they drag along a lot of irrelevant drivers and crud.

> Following is an extract for MDAC v2.0 docs'

> <COPYRIGHT MICROSOFT>

> To have an unattended install that does NOT automatically reboot (it most
> likely needs one though) you can use the following command:
> <mdac Redist> /q /C:"setup /QN1"
> This runs the inner setup in unattended mode and is not automatically
> rebooted. If you really want a minimalist user interface (UI), you can use
> the following command:
> <mdac Redist> /q /C:"setup /QNT"
> To extract the inner setup into a directory, you would use the following
> command:
> <mdac Redist> /t:<path> /c
> Outer Setup Command Line Options
> You can determine the command line options of the outer setup through the
> following statement:

> Command line options for the outer setup include:

>    /Q            - Quiet modes for package.
>    /T:<fullpath> - Specifies Temporary Working folder.
>    /C            - Extract files only to folder when used with /t.
>    /C:<cmd>      - Override install command defined by author.
> After extracting the inner setup to a temporary directory, you can use the
> following command to extract the command line options:

> setup /?
> Command line options for the inner setup include the following:

>    Command Line Option      Description
>    -----------------------------------------------------------------------

>    /A                       Administrator Mode.

>    /G <filename>            Generate logfile of installation activity.

>    /Q[0|1|T]                Quiet install mode (0 shows exit, 1 hides
exit,
>                             T hides all display).

>    /QN[1|T]                 Quiet install mode with reboot suppressed.

>    /R                       Reinstall application (MDAC 1.5 Redistribution
>                             only)

>    /U[A]                    Uninstall the application but leaves shared
>                             components (/UA to remove all).

>    /X <filename>            Set network log location for tracking install
>                             instances.

>    /Y                       Install without copying files.

> <END COPYRIGHTMICROSOFT>

> -------------------------------------------------------------------
> "If you think you know the answer,
> then you don't understand the question !"
> -------------------------------------------------------------------

> > Denny,

> > Thanks for answering my message.

> > I know about MDAC_TYP.EXE. I have a few issues with that route of
> > installation:
> > 1. This includes a whole lot of stuff that my users don't need. I just
> want
> > to install ODBC components. I don't consider this a major problem
though.
> It
> > won't hurt to install everything.
> > 2. The bigger question is the "automatic install". My program will be
> > distributed to professionals in a medical field. While very
sophisticated
> in
> > their own field, many of them are computer phobic. My installation must
be
> > as simple as possible. I want to have a single SETUP.EXE, and have
> > everything install from there. I don't want to have to include
> instructions
> > telling them to run MDAC_TYPE.EXE. Some will freak out.

> > Jim Walsh

> > > I do not know how to make it an automatic step but I belive that
> > > "MDAC_TYP.EXE" is what you need to have the package install.

> > > check the ms site at www.microsoft.com/ODBC/
> > > and it will take you to the MDAC pages.
> > > as I understand it MDAC is Microsoft Data ACcess ...

> > > the self installing exe has a bunch of stuff for ODBC, RDO, ADO etc...

> > > > Does anyone know if there is a Windows Installer Merge Module
> available
> > to
> > > > install the ODBC components? There should be, after all, they're
both
> > > > Microsoft technology.

> > > > Thanks for your help.
> > > > Jim Walsh

> Thanks for answering my message.

> I know about MDAC_TYP.EXE. I have a few issues with that route of
> installation:
> 1. This includes a whole lot of stuff that my users don't need. I just
want
> to install ODBC components. I don't consider this a major problem though.
It
> won't hurt to install everything.
> 2. The bigger question is the "automatic install". My program will be
> distributed to professionals in a medical field. While very sophisticated
in
> their own field, many of them are computer phobic. My installation must be
> as simple as possible. I want to have a single SETUP.EXE, and have
> everything install from there. I don't want to have to include
instructions
> telling them to run MDAC_TYPE.EXE. Some will freak out.

> Jim Walsh

> > I do not know how to make it an automatic step but I belive that
> > "MDAC_TYP.EXE" is what you need to have the package install.

> > check the ms site at www.microsoft.com/ODBC/
> > and it will take you to the MDAC pages.
> > as I understand it MDAC is Microsoft Data ACcess ...

> > the self installing exe has a bunch of stuff for ODBC, RDO, ADO etc...

> > > Does anyone know if there is a Windows Installer Merge Module
available
> to
> > > install the ODBC components? There should be, after all, they're both
> > > Microsoft technology.

> > > Thanks for your help.
> > > Jim Walsh