Converting Access 2000 to 2003

[NEWSGROUPS]

I work for an organization that is migrating from Access 2000 to Access
2003. About 5 or 6 years ago we migrated from Access 97 to Access 2000 with
no problem. Will I have trouble converting these already converted databases
to Access 2003? We also have 2 mda's, will these convert with no problem in
the mda format. We no longer have the mdb that made the mda. Are there any
other nuances that I need to look out for?

Thanks in advance,
Mark

[David W. Fenton]

"NEWSGROUPS " <he******@yahoo .comwrote in
news:fd******** *************** *******@comcast .com:

I had read in another news group posting that I would not be able
to add any code or forms to an Access 2000 database used in Access
2003 unless converted.

No, that's not true. A2K is a native file format for A2K3 (and for
A2K7). The reason is because Jet 4 is shared by all versions of
Access from A2K on. This applies to both pure Jet objects and to
Access objects.

You may have misunderstood posts about the limits of MDEs, which can
only be created from the same version MDB as the version of Access
you are running.

We also have a small subgroup that has already had Access 2003
installed on there workstations and they have reported database
corruptions when accessing an Access 2000 with Access 2003.

Data corruptions? Then you likely have problems outside of Access.
Most of my clients are using A2K-format front ends and back ends,
and running them in A2K, A2K2 and A2K3. There have been no
corruptions of any kind, front end or back end, except in a few
cases with A2K-only setups.

I have also heard that
Access 2003 is a little more "stable" (fewer corruptions etc...).

I don't know about that. I don't consider A2K to be problematic in
this regard, though in its original release it was highly
problematic (Jet 4 SP6 and Access SR1 fixed those problems, but that
was years ago, in 2002 or so).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/