Office 2003 MSI Doesn't Work With Access 97 Installed
I'm about ready to put my fist through the monitor so excuse me if this, my first post, comes off a bit arrogant.
I have created a transform with the ORK CIW tool. Our goal is such that we need to keep Access 97 installed on users' computers. What I'm finding is that whether I tell the transform to leave Access alone or uninstall it, the installation completes but only installs Infopath and Access 2003 and not Word, Excel, Powerpoint, Outlook (even though I've instructed in the transform to NOT install Access!). If I remove Access 97 and run the same transform again, all the apps specified install no problem.
This is with the PRO .MSI that comes on the EA CD from Microsoft.
I have created a transform with the ORK CIW tool. Our goal is such that we need to keep Access 97 installed on users' computers. What I'm finding is that whether I tell the transform to leave Access alone or uninstall it, the installation completes but only installs Infopath and Access 2003 and not Word, Excel, Powerpoint, Outlook (even though I've instructed in the transform to NOT install Access!). If I remove Access 97 and run the same transform again, all the apps specified install no problem.
This is with the PRO .MSI that comes on the EA CD from Microsoft.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
VikingLoki
18 years ago
I'm dealing with this problem right now, and have no solution. A stable installation of Office 97 (even if it's only access) and Office 2003 on the same machine is extremely difficult to pull off.
At this point, I have an Office 97 package (Access + ODBC only) and a full Office 2003 package. Both work, but once the Office 97 package is applied, Access 2003 self-repairs at every launch and doesn't report the component that triggered it. It continues after 97 is uninstalled.
The big problem here is that Office 97 wasn't a windows installer app, and Office 2003 is. As a rule of thumb, whenever you want two versions of the same app inatalled and one is SETUP.EXE and the other MSI, expect to find a royal PIA.
Here are a few gems that you'll run into in this situation:
Access 97 doesn't like Office 2003's HATTEN.TTF font. It blows up with a licensing error, of all things. You must keep the 97 HATTEN.TTF file.
97 & 2003 fight over regkeys in HKLM\CLASSES. Although they do isolate themselves in xxx.8 for 97 and xxx.11 for 2003, there are many "current version" keys that overlap. The 97 and 2003 installs will fight over these keys. Also note that altered registry keys don't trigger self-repairs, only missing keys.
That's about all the info I can give ya at this point. Good luck.
At this point, I have an Office 97 package (Access + ODBC only) and a full Office 2003 package. Both work, but once the Office 97 package is applied, Access 2003 self-repairs at every launch and doesn't report the component that triggered it. It continues after 97 is uninstalled.
The big problem here is that Office 97 wasn't a windows installer app, and Office 2003 is. As a rule of thumb, whenever you want two versions of the same app inatalled and one is SETUP.EXE and the other MSI, expect to find a royal PIA.
Here are a few gems that you'll run into in this situation:
Access 97 doesn't like Office 2003's HATTEN.TTF font. It blows up with a licensing error, of all things. You must keep the 97 HATTEN.TTF file.
97 & 2003 fight over regkeys in HKLM\CLASSES. Although they do isolate themselves in xxx.8 for 97 and xxx.11 for 2003, there are many "current version" keys that overlap. The 97 and 2003 installs will fight over these keys. Also note that altered registry keys don't trigger self-repairs, only missing keys.
That's about all the info I can give ya at this point. Good luck.
Posted by:
PudgeRok
18 years ago
One thing to watch out for when installing Office 2003 is Feature State Migration (FSM). If FSM is enabled (which it is by default), then the Office 2003 setup will install any previous Office feature that has been installed before. The same principle applies to removal. For example, if I have only Word 2000 and Excel 2000 installed, then when I install Office 2003 only Word 2003 and Excel 2003 will be installed (regardless of what is in a transform specified on the command line).
To see if FSM is what is causing your problems, run the installation with the NOFEATURESTATEMIGRATION property set to a value of 1. This will disable FSM for the entire Office suite...if you just want to disable FSM for individual applications, use the checkbox in the Custom Installation Wizard.
More details on FSM can be found in the Office 2003 Resource Kit on Microsoft's web site.
Hope this helps,
Jeremy
To see if FSM is what is causing your problems, run the installation with the NOFEATURESTATEMIGRATION property set to a value of 1. This will disable FSM for the entire Office suite...if you just want to disable FSM for individual applications, use the checkbox in the Custom Installation Wizard.
More details on FSM can be found in the Office 2003 Resource Kit on Microsoft's web site.
Hope this helps,
Jeremy
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
