Access 97 & 02 Upgrade

[hunt4cleanair]

I've got Access 2002 at the office and Access 97 at home, both of which are
incompatible with one another. What version do I need to upgrade to and still
use or convert previous applications to the new version?

 

[Rick Brandt]

I've got Access 2002 at the office and Access 97 at home, both of
which are incompatible with one another. What version do I need to
upgrade to and still use or convert previous applications to the new
version?

2002 can "run" a 97 file as long as it is not an MDE. If you want to be able to
do design work then both machines need to be 2000 or higher.

There will always be MDE compatibility issues going "down". That is, an MDE
created in the 2002/2003 format cannot be run in 2000. Even an MDE created in
2002/2003 format created using 2003 cannot be used in 2002. 2000 and up MDEs
are compatible going "up" though (a 2000 MDE can be run in any higher version).

Any of the newer versions can convert a 97 file to a newer format.

 

[hunt4cleanair]

Thanks Rick...I don't know that it matters both both machines are running XP.
Also, what's an MDE? is that the access suffix...like mdb?

 

[Albert D. Kallal]

Thanks Rick...I don't know that it matters both both machines are running
XP.
Also, what's an MDE? is that the access suffix...like mdb?

"Rick Brandt" wrote:

yes, it is the "suffix", but it means that the application was "complied",
or "frozen" from design changes. Often developers will convert the mdb into
a mde (all versions of ms-access can do this from the tools menu).

the mde is thus as a general rule tided to the particular version of
ms-access. However, a2003 apparently can run a a2000 and a2002 mde without
problems.

Anyway, as mentioned, a2000 to a2003 CAN use a a97 application. And,
further, a2000 to a2003 can CREATE an access a97. So, there is quite a bit
of flexibility in this regards.

So, a97, and a2002 not really incompatible.

If it just data, then leave the file in a97 format. However, if it is an
application, then you should be able to run and open the a97 appcation in
a2002, and NOT have to convert. If you convent the mdb to a2002, then you
obviously can't send it back to the a97 user.

However, there is a option to convert the a2002 back to a97. It would make
no sense to constantly convert this application. I would suggest that you
actually split the database, and then create a version of the program side
(forms, reports) etc for each machine, and then the data can be hared
without modifying it all.

It is not clear if you just trying to move data between each machine, or
have both run and use the data at the same time in a multi-user environment
(this also works quite well if you split...so, you can actually have two
users of diffent versions of ma-success, and yet they can work on the same
data at the same time).

You should be able to run the a97 application on the a2002 machine without
problems. However, if both machines need to use this application and
data...I would suggest you split the appcation, and create a mde for each
computer.

 

[hunt4cleanair]

Albert:

I'm concluding the simple thing is upgrade all computers to 2002 so as I do
either design work or input, I'll be on same system. Likewise, upgrade 97
worksheets to 2002 and maintain in that version...thanks