Re: Will Jet 4.0 connection strings work on XP?

From: Ralph (nt_consulting64_at_address.com)
Date: 09/06/04

  • Next message: Ralph: "Re: Will Jet 4.0 connection strings work on XP?"
    Date: Mon, 6 Sep 2004 14:32:43 -0500
    
    

    Answers inline...

    "Tim Woodward" <tim@trotman.co.uk> wrote in message
    news:191e8699.0409060840.40411e68@posting.google.com...
    > I'm writing some ASP that uses the Jet 4.0 connection string (with an
    > Access 2000 database), which needs to work on all versions of Windows
    > 98 onwards, according to Microsoft Jet 4.0 isn't shipped with MDAC 2.6
    > onwards:
    > http://support.microsoft.com/default.aspx?kbid=271908
    >

    Yes Jet has been removed from the latest 'n greatest MDAC_TYP packages.
    Use the link provided to download the Jet drivers/providers.

    >
    > Does this mean that my ASP code won't work on XP (which comes with
    > MDAC 2.7)?
    >

    I think there might be some confusion about what the MDAC is. It is
    essentially just a package of all the latest 'n greatest data access
    components. ['access' in the generic sense - not MSAccess]. By downloading
    and installing this packages you can upgrade (bug fixes, repairs, new ADO
    object libraries, ODBC drivers, Jet, etc.) in one swoop. This way you don't
    have to worry about upgrading each change or technologies.

    More information:
    http://msdn.microsoft.com/data/DataAccess/mdac/default.aspx

    Not just 'new' stuff is included, like ADO 2.7, but also ADO 2.0, 2.1, 2.5,
    2.6, .... .
    You can install newer MDAC packages as they become available. MDAC packages
    became associated with ADO libraries because that was the primary way of
    upgrading ADO (OLE DB providers too). ie, You want to use the new ADO 2.7 -
    you fetched the new MDAC that included support for ADO, but it still
    contains all the older stuff. (Jet is the exception). In fact iincluding the
    latest 'n greatest MDAC is generally a good idea as it often includes bug
    fixes, security changes, etc. for the older versions.

    Usually a particular MDAC came bundled only with MS Office and Backend
    products. If your particular package used one of the OLE DB providers, or
    used a new library/provider - you installed the MDAC separately as part of
    your install. So whether a particular MDAC is already included on a
    machine - you can always install a newer one.

    So this is a long about way of saying - you can still use ADO 2.6 as long as
    an MDAC is installed that includes that version or higher. The version
    installed with XP includes 2.6.

    M$ stopped including the Jet stuff with the new MDAC packages - making it a
    separate install. (Without going into all the details - it was confusing at
    one time since only new components were included and you had to install
    older versions of MDAC, yadda, yadda, - but you can forget all that.) You
    can download a package that will install the newer Jet from the URL you
    gave.

    So treat MDAC and the Jet Install packages as separate component upgrades,
    that can be included or not include (if already present) with your program
    as your needs dictate. Just load the latest 'n greatest - everything will be
    fine 99% of the time. [There is a possibility of problems with old jet,
    dbase, etc access components - but since you aren't using them - and these
    are rather exotic situations - don't worry about them. <g>]

    >
    > If so what's the alternative that will make the code still work with
    > the older versions on Windows as well as XP?
    >

    Just include the latest MDAC and Jet packages with any install.

    >
    > It seems that Jet is shipped with some other things too though and I'm
    > having difficulty figuring out what, for instance doesn't IE5 come
    > with MDAC 2.5 which then in turn comes with Jet?
    > What ships with IE 6?
    >

    Yes the Jet (especially in the earlier MDAC) is bundled with lots of other
    products that needed those components. Don't worry about it. They were
    included because they were needed with that/those versions of software. Your
    needs may vary.

    Don't worry about what IE includes. At one time M$ used the IE as an
    "unofficial" "service pack" upgrades for Win95/Win98 platforms. Even today
    there are some SPs and products that can't be installed unless IE is
    installed first. (even if you don't use IE).

    Just install the latest 'n greatest MDAC and Jet and you should be fine.

    > Any help appreciated, Cheers.

    I hope this helped - and I didn't take you too far out around the barn. <g>

    Also good reading for working with Jet and MSAccess
    http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300216

    hth
    -ralph


  • Next message: Ralph: "Re: Will Jet 4.0 connection strings work on XP?"

    Relevant Pages

    • Re: Application deployment with Jet Database 4.0
      ... Basically you would install Jet in the same way as MDAC: ... exe that will launch the Jet setup before launching your msi. ...
      (microsoft.public.dotnet.framework.setup)
    • Re: Newbie nervous about OCXes and reliability.
      ... What about the myriad files involved with MDAC? ... If not there then one should supply the VB and C Runtime Redistribution ... packages or have the user download it themselves. ... Install an entire redistribution package just for MSVBVM60.DLL? ...
      (microsoft.public.vb.general.discussion)
    • Re: Newbie nervous about OCXes and reliability.
      ... What about the myriad files involved with MDAC? ... packages or have the user download it themselves. ... Install an entire redistribution package just for MSVBVM60.DLL? ...
      (microsoft.public.vb.general.discussion)
    • Re: Run time error 3706 Provider cannot be found. It may not be properly installed
      ... I have a few questions regarding reinstalling SP2: ... Jet is no longer released with MDAC since Version ... This error is similar to following KB which describes a situation that Jet ... install MDAC 2.5 SP2, and then upgrade to the latest Jet components. ...
      (microsoft.public.data.oledb)
    • Connecting to an mdb
      ... I am a VBA programmer but have something that I think I need done in ... I am wondering about what I need to install to get ... MDAC 2.6 onwards don't include Jet). ...
      (microsoft.public.vb.general.discussion)