You cannot create an Access MDE "compiled" database with Access 2003 that
will run with either the retail or runtime of Access 2000. That is the only
limitation I'd particularly note. In fact, the default file format (unless
you change it) generated by Access 2003 is the Access 2000 file format, but
for MDB or ADP only, not MDE nor ADE.
There may be other, less obvious, or more subtle problems... some people had
obviously had enough difficulties converting Access 97 databases to later
versions that Microsoft released some conversion assistance software for
Access 97 to Access 2003. I'd never had any particular problems with such
conversions, unless there were compile errors in the original (which is easy
to avoid, compile and fix the errors before converting).
Larry Linson
Microsoft Access MVP
"Jeff" <je************@asken.com.au> wrote in message
news:lA****************@news.optus.net.au...
Does anyone know of any potential problems running a 2000 database with
2003?
Also, what about installing all other Office products as 2003 versions but
leaving Access as 2002 running a 2000 database?
Why you ask! A client has a 2000 database. Currently using 2000 runtime
for most employees to work with database. A couple use 2003 to use database,
no problems. They have a mix of versions of other products such as Word,
Excel - 97, 2000 and 2002.
They are considering upgrading everything except Access to 2003, leaving
the Access 2000 runtime and Access 2002 retail in place - because they have
acquired Office 2003 SB (no Access) cheaply. However, they will upgrade
the retail Access to 2003 if they have to - another company looks after this
for them!!!!
Aaaaaaaaaaaaargh
Jeff