Re: problem using Access 2000 database with VB 6.0 app

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

From: Nicholas Couch (blake_at_thecouches.net)
Date: 04/02/04 

Date: 1 Apr 2004 21:23:26 -0800

That did the trick! Thanks for your help. For those who might be
interested, the URL for the service pack download page (the latest SP
is up to 6 now) is:

http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp6/download/

BC

"Phil Hunt" <phung@ktintl.com> wrote in message news:<Od0OlS3FEHA.580@TK2MSFTNGP11.phx.gbl>...
> try install VB6 SP5, if you have not already.
>
> "Nicholas Couch" <blake@thecouches.net> wrote in message
> news:fe440ba9.0403311352.24663597@posting.google.com...
> > Thanks for the suggestion, Jim! Unfortunately, that didn't solve the
> > problem. I'm still getting the "unrecognized database" error. For what
> > it's worth, I even tried creating a new project from scratch, with a
> > single form that has nothing on it but the data control, and when I
> > run the project, I get that same error.
> >
> > For the record, the computer is running XP Pro, with Visual Studio 6.0
> > and Access 2000 installed prior ro undertaking this project.
> >
> > BC
> >
> >
> >
> >
> > "Jim Carlock" <anonymous@127.0.0.1> wrote in message
> news:<OcTjGPuFEHA.2732@tk2msftngp13.phx.gbl>...
> > > Grab the Jet 4.0 stuff and try that:
> > >
> > > http://support.microsoft.com/?KBID=282010
> > >
> > > --
> > > Jim Carlock
> > > http://www.microcosmotalk.com/
> > > Post replies to the newsgroup.
> > >
> > >
> > > "Nicholas Couch" typed:
> > > I am working with a VB 6.0 application that I inherited, and which
> > > currently runs with an Access 97 database and uses DAO code. I need to
> > > have the application start using the same database converted to Access
> > > 2000, but when I try to do this I get the "3343 Unrecognized Database
> > > Format" error on a form that uses the Microsoft data control.
> > >
> > > I've looked at a number of threads that relate to this particular
> > > scenario, and as far as I can tell, I have followed every feasible
> > > suggestion offered to fix this problem. I have changed the project
> > > references to DAO 3.6 from DAO 3.51. I have tried to update the
> > > Connect property of the data control from "Access" to "Access 2000,"
> > > but when I do this I get a runtime error message about a missing
> > > installable ISAM.
> > >
> > > I have yet to find anything that makes this combination of tools work
> > > together properly. Rewriting the application to use ADO instead of DAO
> > > is really not an option. Has anybody had any success making this
> > > scenario (I've got to believe it's a fairly common one) work?
> > >
> > > Thanks in advance for all useful advice!