Access 2007 Runtime on machine with Office 2003.

[Guest]

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!

 

[Stefan Hoffmann]

hi Anders,

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.

Check

http://allenbrowne.com/bug-17.html


mfG
--> stefan <--

 

[Stefan Hoffmann]

hi,

Solution greatly appreciated!

As my other post may be not that helpful, go google for

http://groups.google.de/groups/search?q=access+2007+runtime+office+2003&qt_s=Groups-Suche

It is and was never a good idea to run different Office versions on one
system, even if it is possible with some hacks (e.g. the font hack for
installing Access 97 and 2000). Just my 2 cent.

mfG
--> stefan <--

 

[Rick Brandt]

hi,

As my other post may be not that helpful, go google for

http://groups.google.de/groups/search?q=access+2007+runtime+office+2003&qt_s=Groups-Suche

It is and was never a good idea to run different Office versions on
one system, even if it is possible with some hacks (e.g. the font
hack for installing Access 97 and 2000). Just my 2 cent.

mfG
--> stefan <--

I would qualify that statment a bit. Up to now it was not much of a problem to
install an Access runtime on a PC that already had a different version of
*Office* on it as long as that PC did not have a different version of *Access*
on it (most versions of Office do not include Access). Even with mixing Access
versions the issues raised were not that big of a deal (if you knew about them).

It is only with 2007 that having any other Office app in another version on the
same PC causes big headaches. This (IMO) lowers considerably the value of even
having a runtime version of Access. Microsoft apparently came to that same
conclusion and doesn't even charge for the 2007 runtime tools.

I believe the main problem was "improved", but to what extent I don't know.

 

[Stefan Hoffmann]

hi Rick,

I would qualify that statment a bit. Up to now it was not much of a problem to
install an Access runtime on a PC that already had a different version of
*Office* on it as long as that PC did not have a different version of *Access*
on it (most versions of Office do not include Access). Even with mixing Access
versions the issues raised were not that big of a deal (if you knew about them).

This is true.

To make it clear, this is really my own opinion.

It is only with 2007 that having any other Office app in another version on the
same PC causes big headaches. This (IMO) lowers considerably the value of even
having a runtime version of Access. Microsoft apparently came to that same
conclusion and doesn't even charge for the 2007 runtime tools.

The problems here are legion - at the first glance. But some are by
design, so we have to learn how to deal with them.


mfG
--> stefan <--

 

[Guest]

This is really BAD NEWS. Almost everybody has Office installed on their
computers. How to sell an application which causes Office to require the
installation CD on startup?!!

I feel that it is almost impossible to get in touch with Microsoft. On their
support pages they refer to this forum, but I haven't seen anyone
representing Microsoft here.

I've also mailed Clint Covington from the Access team, but I get no reply.

Where can I get in touch with them???