/build/static/layout/Breadcrumb_cap_w.png

Access 2003 Issue

Hi all,

Got some workstations out that have Office 2003 on them without Access 2003. We need to deploy Access 2003 to them now, we dont have Access 2003 standalone install, just the Office 2003 Pro disc.

I have tried to use Microsoft's Custom Install Wizard, I select I dont want to install Word..etc.. as they are already installed. So I just select Access 2003. It creates a MST for me, so I goto run it with the MSI and it does not install. I check the log file, and it goes to use the MST I made, but reverts back to the standard MST not mine.


Any ideas on how to install Access 2003 without uninstalled the other Office Products.

Cheers all

0 Comments   [ + ] Show comments

Answers (8)

Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
ORIGINAL: Thegunner
Got some workstations out that have Office 2003 on them without Access 2003. We need to deploy Access 2003 to them now, we dont have Access 2003 standalone install, just the Office 2003 Pro disc.

I have tried to use Microsoft's Custom Install Wizard, I select I dont want to install Word..etc.. as they are already installed. So I just select Access 2003. It creates a MST for me, so I goto run it with the MSI and it does not install. I check the log file, and it goes to use the MST I made, but reverts back to the standard MST not mine.

Any ideas on how to install Access 2003 without uninstalled the other Office Products.


from the command line I think you need to do REINSTALLMODE=vomus ADDLOCAL=MSAccess (find the name of the parent feature of all access components and put it here)
Posted by: jmcfadyen 15 years ago
5th Degree Black Belt
0
you can use the sessionobject to update the feature state of features in the application.

from the top of my head its something like this

const msiFeatureStateLocal = xx (you will need to look this one up)

set objInstaller = CreateObject("Windowsinstaller.installer")
objInstaller.ConfigureFeature "product code goes here", "featurename goes here", msiFeatureStateLocal


this is untested although i have used this method many many times in the past.
Posted by: jmcfadyen 15 years ago
5th Degree Black Belt
0
sorry correction its the installer object and you will need these






msiInstallStateAdvertised

The feature is advertised


msiInstallStateLocal

The feature is installed locally.


msiInstallStateAbsent

The feature is uninstalled.


msiInstallStateSource

The feature is installed to run from source.


msiInstallStateDefault

The feature is installed to its default location.
Posted by: NOxxie 15 years ago
Senior Yellow Belt
0
Best i have seen and made it work with 2003 and 2007 is creating a MSP file for adding the Access 2003 setup.

ORK Tools does not supply the answer here to "add ontop" of a current setup.

Regards,

NOxxie
Posted by: Thegunner 15 years ago
Second Degree Green Belt
0
Hi all,
So far I have got it to install by doing the following.

msiexec /i pro11.msi ADDLOCAL=ACCESSFiles

and it installs, but it does not put a shortcut in the Start Menu. Any ideas, I have tried a few things but to no avail.

Cheers
Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
try logging it to find out why the sc is not installed. should be if it's a part of that feature. what does the ORK show?
Posted by: Thegunner 15 years ago
Second Degree Green Belt
0
Will give it a go and see what happens.Any other ideas in the mean time I could try?
Posted by: Thegunner 15 years ago
Second Degree Green Belt
0
Sorted, Use the CMW tool instead of the CIW. This will modify he install of office, to include Access.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ