Access 97 under Win 2k to Access 2003 under XP

[mscertified]

I'm in a shop converting a large number of Access databases (over 500) for a
large number of users. Some databases have one user, some have dozens.
The rollout of XP is happening in a random manner, so we'd like to do some
conversions before the users get XP. I figured we could convert the 97
databases using Access 2003 and save as a Win 2000 compatible mdb. Then when
the users do get converted we simply generate a Windows 2003 mde. Are there
any issues in testing a system as a Win 2k mdb then unleashing a 2003 mde or
should it be plain sailing. Thanks - David.

 

[Albert D.Kallal]

I'm in a shop converting a large number of Access databases (over 500) for
a
large number of users. Some databases have one user, some have dozens.
The rollout of XP is happening in a random manner, so we'd like to do some
conversions before the users get XP. I figured we could convert the 97
databases using Access 2003 and save as a Win 2000 compatible mdb

I never head the term win 2000 compatible mdb. Those mdb can be placed on a
Linux server, or even a novel server, and STILL function correctly. So, the
mdb file format has no relation whatsoever to the operating system???

Perhaps you mean that you are going to use access 2003 on win2k box, but the
end users will have windows XP? This should work ok. I would feel "better"
if I was testing and deploying from the same OS, but in your case, I think
windows 2000 should be a ok development platform, but deploying to windows
xp.

There is most certainly a issue of what version of ms-access runs with what
system, but the above use of the term "win 2000 mdb" don't make sense (you
might want to clarify what you mean here).

. Then when
the users do get converted we simply generate a Windows 2003 mde. Are
there
any issues in testing a system as a Win 2k mdb then unleashing a 2003 mde
or
should it be plain sailing. Thanks - David.

If you are going to run some of the multi-user application in a mixed
environment you can. In other words, both the access97 applications, and the
access 2003 applications can use the SAME data. this assumes a split
database of course. I have companies roll out new pc's over time, and there
were AMAZED that some machines could run a97, and others running access 2003
at the same time on the same data. (most have had horror stores about
ms-access,and in fact we were BETTER then the other software vendors on
site...as they had MUCH more problems then us!!).

 

[mscertified]

Please substitute the term 'Access 2000 compatible mdb' for 'Win 2K
compatible mdb'. We will be developing on XP machine with Office 2003 and
Access 2003 but saving as Access 2000 compatible mdb. This will be tested by
users in Windows 2000. After OS conversion to XP, we will then implement
after compiling the unchanged database to an Access 2003 mde. This is the
process I am hoping will be error-free.

David

 

[Albert D.Kallal]

Please substitute the term 'Access 2000 compatible mdb' for 'Win 2K
compatible mdb'. We will be developing on XP machine with Office 2003 and
Access 2003 but saving as Access 2000 compatible mdb. This will be tested
by
users in Windows 2000. After OS conversion to XP, we will then implement
after compiling the unchanged database to an Access 2003 mde. This is the
process I am hoping will be error-free.

Ok, I have to assume then that some machines will have access 2000 on them?

Even I substitute the term access 2000 compatible mdb here, this still does
not tell me you are running access 2000 on those boxes? (I guess, I have to
assume yes???).

So, if there is no access 2000 involved, then simply jump to access 2003
(the formats are in NO way connected to the OS). And, you can run access
2003 on both windows 2000, and xp.

However, if your question is can you develop a a2000 application with a2003,
and then deploy that application to machines with access 2000 installed?

You can, but you need to be aware of two things:

1) You can't make a access 2000 mde with access 2003

2) If you are going to deploy a access 2000 file to a pc wit access
2000, but developed with a2003, then you need to do a de-compile

You then need to re-compile the 2000 mdb on a machine that is running
access 2000. Many find that you don't have to do this, but since they are
not binary compatible, I would do this (you get better luck going
forward...and a2003 can consume a a2000 file). So, I don't recommend going
the reviser. (I currently support a few clients running a2000, but use a2003
on my machine (in a2000 format). I find the applications don't run, or
behave well at all if you don't de-compile...and re-compile on the box
running a2000. And, since you have to re-compile, then you can distribute a
mde at that point anyway...


So, development of a a2000 application with a2003 works just fine..but when
you deploy to machines with access 2000, you need to de-compile..and then
re-compile the application.

And, by the way, many of us developers have 2, or even 3 versions of
ms-access installed on the same pc. So, you can put a2000 on your
development box if you want. However, since you ARE going to be deploying to
both a2000, and a2003 users (but in a2000 format), then likely staying with
a2003 is a good choice.