Access 2002 can natively use the Access 2000 format, so yes, you can
maintain the database in 2002. Naturally you need to avoid the things that
were new in 2002, such as OpenArgs for OpenReport.
Every version of Access uses a different binary for the compiled code. This
means you cannot release an MDE in A2002 if the file format is A2000.
It also means that after developing in A2002, an A2000 MDB will be
automatically recompiled into the A2000 binary format when run in that
version. Well, that's the theory anyway: in practice, this doesn't work
100%, and you can end up with weird and even intermittent errors that show
up on some machines and not on others. To avoid that, decompile your mdb
before giving it to the client. (Ideally you would recompile in A2000, but
you don't have that option.)
To decompile, make a copy of the database, and enter something like this at
the command prompt while Access is not running. It is all one line, and
include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Then compact the database.
For a list of the kinds of issues you could strike when moving an A97 mdb to
a later version, see:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://allenbrowne.com/ser-48.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Richard Cleaveland" <Ne************@rgcle.com> wrote in message
news:Le********************@comcast.com...
A client has just successfully upgraded from Access 97 to 2000. I don't
have Access 2000, but I do have Office XP. Can I successfully use my
Access
on their database? They kind of did this behind my back, and I'm
responsible
for the application maintenance...!
Dick