DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 5 of 5

Thread: When is mdac_type.exe needed?

  1. #1
    Ted Young Guest

    When is mdac_type.exe needed?


    I am trying to create a setup package for a VB6 application that uses DAO.


    I am trying to ensure that the exe/cab files are as small as possible. I
    have found that the mdac_typ.exe is very large. I am not sure when a user
    needs this.

    When does this file need to be included in the setup?

    I found some info on MSDN (see below) that seems to indicate this is only
    needed for ADO. Is this correct?

    Would the assumption that using DAO instead of ADO results in a smaller install
    be correct?

    Thanks!

    Ted


    MSDN Article:
    -------------
    If your application uses one of Visual Basic's data access technologies,
    such as Data Access Objects (DAO), ActiveX Data Objects (ADO), or Remote
    Data Objects (RDO), the Package and Deployment Wizard performs two additional
    steps during the packaging process:

    If your application uses ADO, OLEDB, or ODBC components, the wizard automatically
    adds a file called mdac_typ.exe to the list of files to include in your package.
    Mdac_typ.exe is a self-extracting executable that installs all of the necessary
    components you need for your data access technology.

    The wizard prompts you to choose the appropriate data access option when
    your application includes DAO features. You choose the appropriate method
    - ISAM-based, ODBCDirect, ODBC through Jet, etc.



  2. #2
    Eric D. Burdo Guest

    Re: When is mdac_type.exe needed?

    mdac_typ.exe includes the latest DAO. I believe that according to Microsoft, you have to
    use mdac_typ to distribute the DAO components...

    --

    Eric D. Burdo, Red-Leif International
    VB Programmer and Consultant
    <http://www.redleif.com/vb>

    *** Please reply to the newsgroup so all can benefit. ***


    "Ted Young" <tedyoung@connecticare.com> wrote in message news:3a78145a$1@news.devx.com...
    >
    > I am trying to create a setup package for a VB6 application that uses DAO.
    >
    >
    > I am trying to ensure that the exe/cab files are as small as possible. I
    > have found that the mdac_typ.exe is very large. I am not sure when a user
    > needs this.
    >
    > When does this file need to be included in the setup?
    >
    > I found some info on MSDN (see below) that seems to indicate this is only
    > needed for ADO. Is this correct?
    >
    > Would the assumption that using DAO instead of ADO results in a smaller install
    > be correct?
    >
    > Thanks!
    >
    > Ted
    >
    >
    > MSDN Article:
    > -------------
    > If your application uses one of Visual Basic's data access technologies,
    > such as Data Access Objects (DAO), ActiveX Data Objects (ADO), or Remote
    > Data Objects (RDO), the Package and Deployment Wizard performs two additional
    > steps during the packaging process:
    >
    > If your application uses ADO, OLEDB, or ODBC components, the wizard automatically
    > adds a file called mdac_typ.exe to the list of files to include in your package.
    > Mdac_typ.exe is a self-extracting executable that installs all of the necessary
    > components you need for your data access technology.
    >
    > The wizard prompts you to choose the appropriate data access option when
    > your application includes DAO features. You choose the appropriate method
    > - ISAM-based, ODBCDirect, ODBC through Jet, etc.
    >
    >




  3. #3
    Ted Young Guest

    Re: When is mdac_type.exe needed?


    Can anyone verfiy this?

    All doc I find seems to indicate that mdac_type.exe is not needed if DAO
    is being used as the Data Access tool.


    "Eric D. Burdo" <vbtips@redleif.com> wrote:
    >mdac_typ.exe includes the latest DAO. I believe that according to Microsoft,

    you have
    >to
    >use mdac_typ to distribute the DAO components...
    >
    >--
    >
    >Eric D. Burdo, Red-Leif International
    >VB Programmer and Consultant
    ><http://www.redleif.com/vb>
    >
    >*** Please reply to the newsgroup so all can benefit. ***
    >
    >
    >"Ted Young" <tedyoung@connecticare.com> wrote in message news:3a78145a$1@news.devx.com...
    >>
    >> I am trying to create a setup package for a VB6 application that uses

    DAO.
    >>
    >>
    >> I am trying to ensure that the exe/cab files are as small as possible.

    I
    >> have found that the mdac_typ.exe is very large. I am not sure when a

    user
    >> needs this.
    >>
    >> When does this file need to be included in the setup?
    >>
    >> I found some info on MSDN (see below) that seems to indicate this is only
    >> needed for ADO. Is this correct?
    >>
    >> Would the assumption that using DAO instead of ADO results in a smaller

    install
    >> be correct?
    >>
    >> Thanks!
    >>
    >> Ted
    >>
    >>
    >> MSDN Article:
    >> -------------
    >> If your application uses one of Visual Basic's data access technologies,
    >> such as Data Access Objects (DAO), ActiveX Data Objects (ADO), or Remote
    >> Data Objects (RDO), the Package and Deployment Wizard performs two additional
    >> steps during the packaging process:
    >>
    >> If your application uses ADO, OLEDB, or ODBC components, the wizard automatically
    >> adds a file called mdac_typ.exe to the list of files to include in your

    package.
    >> Mdac_typ.exe is a self-extracting executable that installs all of the

    necessary
    >> components you need for your data access technology.
    >>
    >> The wizard prompts you to choose the appropriate data access option when
    >> your application includes DAO features. You choose the appropriate method
    >> - ISAM-based, ODBCDirect, ODBC through Jet, etc.
    >>
    >>

    >
    >


  4. #4
    Phil Weber Guest

    Re: When is mdac_type.exe needed?

    > Can anyone verfiy this?

    Ted: Try these (found by searching for "distribute dao" at
    http://support.microsoft.com ):

    INFO: Deploy Database Applications with the Package
    and Deployment Wizard (PDW)
    ( http://support.microsoft.com/support.../q213/8/46.asp )

    HOWTO: Ensure Jet 3.5 Is Installed Correctly (Part I)
    ( http://support.microsoft.com/support.../q240/3/77.asp )

    ---
    Phil Weber



  5. #5
    Joe \Nuke Me Xemu\ Foster Guest

    Re: When is mdac_type.exe needed?

    "Eric D. Burdo" <vbtips@redleif.com> wrote in message <news:3a7820a4$1@news.devx.com>...

    > mdac_typ.exe includes the latest DAO. I believe that according to Microsoft, you have to
    > use mdac_typ to distribute the DAO components...


    This used to be true, but newer versions of mdac_typ no longer include
    DAO, which is now in separate installs, just to make our lives that
    much more interesting:

    <http://www.microsoft.com/data/download.htm#Jet4SP3info>

    Presumably, you'll need to install Jet 4.0 Service Pack 5 on top of
    that and possibly Jet 3.x Service Pack 3 as well. Don't forget about
    JetComp or the files that are dumped into windows\system instead of
    the proper replication manager directories! I have little choice but
    to assume MS is pushing us towards MSDE by making Jet as hellish as
    possible to install properly, as a stepping stone to SQL Pervert on
    Winblows $2000 Pervert when you get sick of rolling out monster MSDE
    service packs to all your workstations.

    Where do you want to get boned today?

    --
    Joe Foster <mailto:jfoster@ricochet.net> Got Thetans? <http://www.xenu.net/>
    WARNING: I cannot be held responsible for the above They're coming to
    because my cats have apparently learned to type. take me away, ha ha!



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center