2003 and 97 Access on the same machine

[Steven]

I have Access 2003 at home but I want to work on some Access 97 mdbs at home
also without converting them.

1). Can I put Access 97 on the same machine as the Access 2003 without some
hazardous conflict occuring? And then I could work on the Access 97 files
independent of the 2003 version..Correct?

2). How will the system know that the 97 files are to run with the Access
97 version or how do I direct it if it does not happen automatically?

3). Is Access 97 ok under Windows XP?


Thanks for your help.

Steven

 

[Ofer]

1. I do, I have both on the same computer, no problem
2. Open Access first and then select the MDB, or, if you open through the
explorer, then right click with the mouse, and select the program you want to
run the mdb with.
In general in my window xp, it keep in its memory which Access version I
opened last, and that is the default.
3. I do, no problem

 

[Tony Toews]

I have Access 2003 at home but I want to work on some Access 97 mdbs at home
also without converting them.

I also have A2000 and A2002 on my system. Along with, briefly, A2.0
to test a problem someone was having.

1). Can I put Access 97 on the same machine as the Access 2003 without some
hazardous conflict occuring? And then I could work on the Access 97 files
independent of the 2003 version..Correct?
Yes.

2). How will the system know that the 97 files are to run with the Access
97 version or how do I direct it if it does not happen automatically?

You can add explicit path and file names of the appropriate versions
of access to all the shortcuts. For example "C:\Program
Files\Microsoft Office 97\Office\msaccess.exe". Including the quotes
if you have any spaces in the path name which is very likely.

There are some programs out there which will automatically start the
appropriate version of Access.

One of those is ACCVER - Allows you to work with multiple versions of
MS Access databases. Detects the version of Access used to create your
MDB, MDE or MDA files and either reports the version number or starts
the appropriate version of MS Access.
http://www.aylott.com.au/accver.htm

Also see: INFO: Access 2000/Access 97 Coexistence FEPs (Frequently
Experienced Problems)
http://www.trigeminal.com/usenet/usenet019.asp?1033
Subject: INFO: Avoiding the default system.mdw loss when
re-registering Access 97
http://www.trigeminal.com/usenet/usenet018.asp

3). Is Access 97 ok under Windows XP?

Been working fine for me under Win XP for years. My largest FE MDB
has 450 forms and 350 reports. Or was it 350 forms and 450 reports?
I can't recall now.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[TC]

Each version of Access registers itself (as the current version of
Access) when you start it directly. So I just have a shortut on the
desktop for msaccess.exe (97), and another for msaccess.exe (2003, or
whatever). When I want to work in 97, I just run the 97 shortcut, then
close Access. From then on, opening an mdb file (and so on) will
automatically use Access 97. When I want to work in 2003, I just run
the 2003 shortcut (then close Access); and so on.

Jst be sure yo do not install the two versions to the same directory!
That will certainly screw things up. Standard practice is to install
the different versions in version order (97, then 2000, etc.) in
/different directories/.

HTH,
TC [MVP Access]

 

[Tony Toews]

Jst be sure yo do not install the two versions to the same directory!
That will certainly screw things up.

Ah, yes, I keep forgetting to state that.

Standard practice is to install
the different versions in version order (97, then 2000, etc.) in
/different directories/.

Standard practice but not required. I've deliberately installed
Access 97, 2000, 2002/XP and 2003 out of sequence the last four or
five installs. And in a different sequence each time. Other than
the License problem I've never had a problem.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[TC]

Ok, I'll note the "order" thing, thanks for that info.

Cheers,
TC [MVP Access]

 

[JFXV]

A tip:
When you need to use sometime old versions of software, you better can
use a virual machine like VMWare. Then you can install the software
with its original operatingssystem and then use it. Also when you buy a
new computer you only have to install VMWare again and copy the image
and use it again.

 

[Tony Toews]

When you need to use sometime old versions of software, you better can
use a virual machine like VMWare. Then you can install the software
with its original operatingssystem and then use it. Also when you buy a
new computer you only have to install VMWare again and copy the image
and use it again.

Good point. However I flip between versions in one day that that
could get rather irritating.

Now there are problems with multiple versions of MOD and ODEs being on
the same system. So I use Virtual PC/VMWare to build those. And to
test the installs especially if OCXs or DLLs are distributed.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm