2 loaded versions of Office on one Machine

[ajetrumpet]

Per the title of this thread, I am wondering what kind of errors would go on with this situation. Right now I have this on my machine, but other than the installation of a few files when I switch back and forth from version to version of Access only, there doesn't seem to be much of a problem with it.

What I am wondering is this: If I offered advice to 3rd parties about their software and general use of Office products, and perhaps needed to consult them or even write a bit of code for their operation, would I be in jeopardy by using this machine of mine to testrun my coding and such? I am wondering how much of an impact the two version-installation thing would have on my "testing" of different code products, and general integration of MS Office program usage on other machines with the same operating system...

 

[gemma-the-husky]

adam

i have A97, AXP(2002) A2003, and A2007 all on one machine with no problems

A97, AXP and A2003 co-reside quite happily - all that happens is that any mdb tries to load with the last used version, which is sometimes the wrong one

A2007 changes things a bit, as it interferes with the others, so that they need to reinstall/reconfigure as you switch between them, but no operational difficulties, other than A2007 has an awful look and feel, IMO

A97 gets installed in folder c:\program files\microsoft office\office
AXP gets installed in folder c:\program files\microsoft office\office10
A2003 gets installed in folder c:\program files\microsoft office\office11
A2007 gets installed in folder c:\program files\microsoft office\office12

 

[ajetrumpet]

all that happens is that any mdb tries to load with the last used version, which is sometimes the wrong one

I am thinking that is the only thing that will be wrong with my situation too. Thank you Gemma. It is reassuring...

 

[AngelsGuardian]

Once you get to recognise the icon of each version, when you open a mdb you right click and select with what version you want it to open with !

 

[Len Boorman]

You can tweak the shortcut to call the correct MSACCESS.exe

L