A
anders1977
This message is meant for someone in the Access Team at Microsoft.
I have made an application using Access 2007. When running the application
using 2007 Runtime on a machine which has Office 2003 installed, a
potentially BIG problem occurs.
The 2007 application runs fine. The problem arises when I start an Office
2003 program afterwards. During startup, the program will go through a
2-minute configuration screen, and it also prompts the user for the Office
2003 CD-ROM. This happens every time I have been running the Access 2007
Runtime application, and then starts Office 2003. How to avoid this?
I've seen a post somewhere else on the internet about a change in a registry
key, but I don't want to change the registry unless I absolutely have to.
I feel that Access 2007 is next to useless as a platform for retail
products, as long as this issue resides. My application is ready for sale,
but I dare not do it yet because of this. Most companies are still running
Office 2003 or older.
Solution greatly appreciated!
I have made an application using Access 2007. When running the application
using 2007 Runtime on a machine which has Office 2003 installed, a
potentially BIG problem occurs.
The 2007 application runs fine. The problem arises when I start an Office
2003 program afterwards. During startup, the program will go through a
2-minute configuration screen, and it also prompts the user for the Office
2003 CD-ROM. This happens every time I have been running the Access 2007
Runtime application, and then starts Office 2003. How to avoid this?
I've seen a post somewhere else on the internet about a change in a registry
key, but I don't want to change the registry unless I absolutely have to.
I feel that Access 2007 is next to useless as a platform for retail
products, as long as this issue resides. My application is ready for sale,
but I dare not do it yet because of this. Most companies are still running
Office 2003 or older.
Solution greatly appreciated!