Access 2000 vs. 2003

D

DaveM

We have a current VB6 application using ado on an Access 2000 db. Are there
advantages to upgrading our DB to 2003 format? Are there ANY Sytax
differences or anything at all we should be aware of that may cause conflicts
of any kind?
Responses are greatly appreciated.
 
B

Brian

DaveM said:
We have a current VB6 application using ado on an Access 2000 db. Are there
advantages to upgrading our DB to 2003 format? Are there ANY Sytax
differences or anything at all we should be aware of that may cause conflicts
of any kind?
Responses are greatly appreciated.
Click to expand...

Sound to me like a classic case of "if it ain't broke, don't fix it".
 
N

Norman Yuan

Beisdes generic wisdom said in the other post ("if it ain't broke, don't fix
it"), consider this:

Since you access data in the Access database (more accurately, JET database)
in a stand-alone VB app (through ADO or DAO, right?), the data access is
handled by JET engine, not Access Application (the Access Program). Although
each version of Access (the program) has its own file format, the database
engine JET stays in its version 4.0 since late 90s (Access2000) and will not
be changed any more untill it dies naturally, as MS intends to do. Now that
your VB app access data in that *.mdb file through Jet engine, which can
read all version of *.mdb file (or at leat most of, I am not should if there
is problem for the very first or second version of Access file or not), the
*.mdb format 2000, 2002, or 2003 does not matter to your VB app. You may
want to apply latest JET service pack (SP8?), though.
 
Top