Quote: Originally Posted by Saurabh A
... However, please share if that is a safe setup? Would you recommend 'basils57' to continue using 'Office' the way it is setup, or do you advise any changes? (In absence of a Virtual Machine)
I have been deploying Access application for over 15 years now. There has always been issues with multiple version of Access installed. It does not mater if the mix is with the Full/retail version and/or the Runtime versions. Starting with Access 2000 most components were installed in a separate sub folder under "Microsoft Office". Access 97 was a different. You must install it in a different folder than later versions. End Users:
If it is an end user using just a compiled database (mde or accde) they generally have few if any issue other than the "reinstall" when they switch versions. Developers:
The main issues I see is when you are doing development with multiple versions installed.
The issue arises from the "C:\Program Files\Common Files\microsoft shared" and/or "C:\Program Files (x86)\Common Files\microsoft shared". This can cause issues with Library references when you deploy the Access application.
When developing on a machine with Multiple version of Access I find it critical to always test my deployment files on a machine with only a single version of Access installed. A VM is great for that.
In the end, if you are doing development with multiple versions of Access installed you will need multiple machines. You need a machine with only a single version of Access installed. I find using VMs the most efficient and economical. The ability to roll back a VM is great for keeping a clean testing environment.