VB and the different Access MDB versions

[Kyle Jedrusiak]

We have multiple apps that were written in VB5, brought up to VB6 and make
use of both DAO and ADO in different spots. [Several people along different
learing curves made changes as part of many revolving design changes].

However the back end data for these apps all currently resides in an Access
97 format MDB file.

Since there are still minor changes being made until the decision is made to
re-architect the whole thing using SQL and .NET we are trying to at least
eliminate Access 97.

If we convert the MDB files to a Access 2000 format (or preferably Access
2002 format), how much trouble would it be to get our applications to
support the new MDB format.

I kind of know it will involved selecting newer ADO libraries, etc. and
re-compiling But am I opening up a huge can of worms here?

Kyle!

 

[Douglas J. Steele]

Depending on whether you're using bound controls or not, it could be as
simple as changing your DAO reference from 3.5 to 3.6, and changing your ADO
provider from Microsoft.Jet.OLEDB.3.51 to Microsoft.Jet.OLEDB.4.0

Check the following for resolutions to some of the problems you could
encounter:
PRB: Error "Unrecognized Database Format" When You Upgrade to Access 2000 or
2002:
http://support.microsoft.com/?id=238401
FIX: The Data Form Wizard May Not Open an Access 2000 Database:
http://support.microsoft.com/?id=242010
HOWTO: Modify the Visual Data Manager (VISDATA) to Work with Access 2000
Databases:
http://support.microsoft.com/?id=252438
FIX: Unrecognized Database Format Error with Data Control or Data Form
Wizard:
http://support.microsoft.com/?id=257780

On the other hand, I don't really understand the point of upgrading just for
the sake of upgrading. If it ain't broke, don't fix it!

 

[david epsom dot com dot au]

Jet 3.5 stopped with SP2, SR3, in 1999. Any bugs you
got are the bugs you had. DAO 3.5 also stopped.

Jet 4.0 is now up to SR7/SR8, and each release has
been necessary to fix bugs. Each release has had
minor changes (for example, compact no longer resets
autonumber fields). You get new releases if you want
it or not: the last Win2000 service pack included a
new release of Jet. After 4 years, we are still
fiddling with our Access Applications to get them
to work properly, and some of that may be down to
changes in the database engine. With the exception
of Unicode, the new features of Jet 4 are flaky,
and should be avoided.

On the other hand, Jet 4 supports Unicode data, and
a new version of ADO may one day break Jet 3.5.
You take your chances.

(david)