Re: Creating an Office XP compatible database?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Phillip Windell (_at_.)
Date: 03/30/04 

Date: Tue, 30 Mar 2004 16:09:21 -0600

You need to use Jet 4.0

My VB6.0 has Jet 3.51 and 4.0 and I didn't do anything special to make it
happen that way. I suppose just updating to the newest MDAC Components you
can run on your machine will do it,..that is all I have ever done.

If your current MDAC is older than 2.5, I believe I upgraded it with
MDAC2.5-SP2 first then went up to MDAC2.7. There was a "cutoff" in there
somewhere where the Jet engine wasn't included. Version 2.5 sp1 may have
been the last one to include it. The details are fuzzy to me, but MS's site
should have the details when you find thier MDAC "stuff". 

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"dkomo" <dkomoNoSpam@cris.com> wrote in message
news:4069F177.89F251AB@cris.com...
> I wrote a VB 6.0 program to create an Access database file and fill it
> with data. I used the following DAO statement:
>
>      Set db_AllEquity = ws.CreateDatabase(Database_Name,
>                           dbLangGeneral, dbVersion30)
>
> On my older computer I can open the .mdb file with Office 97 Access
> with no problem
>
> Then I took the program over to my notebook, which runs under Windows
> XP Pro and has Office XP installed, recompiled the program, and
> recreated the .mdb file.  Much to my surprise, Access in Office XP put
> out a message saying the it needs to run a conversion on the .mdb file
> to make it compatible with Access 2000 and Access 2002.
>
> Does anyone know what's going on here?  I have all the latest system
> components installed on the notebook.  According to the VB 6.0 online
> manual, the constant dbVersion30 specifies the Microsoft Jet database
> engine version 3.0 file format (compatible with version 3.5).  This is
> the most recent version available to VB 6.0.
>
> What do I need to do to create an Access .mdb file compatible with the
> version of Office XP (2002) that I have?
>
>
>      --dkomo@cris.com

Relevant Pages

  • Re: Creating an Office XP compatible database?
    ... I suppose just updating to the newest MDAC Components you ... somewhere where the Jet engine wasn't included. ... > Then I took the program over to my notebook, which runs under Windows> XP Pro and has Office XP installed, recompiled the program, and> recreated the .mdb file. ...
    (microsoft.public.vb.database)
  • Re: Microsoft and trust
    ... Jet was separated from MDAC because MDAC components were not required by ... Jet has been in the MDAC packages for many versions. ...
    (microsoft.public.vb.general.discussion)
  • MDAC
    ... For my NET app need Jet, connected to mdb file with OLEDB connection. ... MDAC 2.5., not in MDAC 2.6 or 2.7. ...
    (microsoft.public.dotnet.distributed_apps)
  • MDAC ADO ??
    ... For my NET app need Jet, connected to mdb file with OLEDB connection. ... MDAC 2.5., not in MDAC 2.6 or 2.7. ...
    (microsoft.public.dotnet.distributed_apps)
  • MDAC JET 4.0
    ... For my NET app need Jet, connected to mdb file with OLEDB connection. ... MDAC 2.5., not in MDAC 2.6 or 2.7. ...
    (microsoft.public.data.ado)