Access 2010 Runtime Silent Install

B

Bob Howard

Well, it looks like we're only 2+ weeks away from Access 2010 (and Runtime)
being made public / available. To date, I've not stumbled on anything that
gives me an option to silently install Runtime. It's packaging is very
different from before as it uses an XML-based installation scheme.

It seems that the problem lies in that the self-extractor (phase 1)
immediately passes control to the installer (phase 2) without giving me any
opportunity to add to (or modify) the XML (just extracted) that controls the
installation. There seems to be a command line parm that "could be" passed
to the phase 2 installer pointing it to some override XML, but the problem
is that I've yet to discover how to tell the self-extractor (phase 1) to
pass that parm --- it just executes it (with no parm) as soon as the
extraction completes.

I have not found any documented parms for the self-extractor program.

I've had some communication with the person at MS responsible for Runtime.
We exchanged a few emails (several months ago) but all proved fruitless.

Has anyone gotten any further than I have (anything would be further than I
have!).

bob h.
 
G

Grubsi

hi bob,

extract the runtime using the extract switch e.g.: "AccessRuntime 2010
ENG.exe" /extract:C:\AccessRT
create a config xml file with the following content in the folder
where the extracted files are (file name e.g. config.xml):
<Configuration Product="AccessRT">
<Display Level="Basic" CompletionNotice="no" SuppressModal="yes"
AcceptEula="yes" />
<!-- <Logging Type="standard" Path="C:\Temp\"
Template="Microsoft_Access_2010_Runtime_Setup(*).log" />
<COMPANYNAME Value="Company Name" /> -->
<Setting Id="SETUP_REBOOT" Value="IfNeeded" />
</Configuration>

you can also specify a logfile location and a company name, just
uncomment the two lines.

than run setup.exe in the same folder:
setup.exe /config config.xml

stefan
 
R

Richard (rhw)

hi bob,

extract the runtime using the extract switch e.g.: "AccessRuntime 2010
ENG.exe" /extract:C:\AccessRT
create a config xml file with the following content in the folder
where the extracted files are (file name e.g. config.xml):
<Configuration Product="AccessRT">
<Display Level="Basic" CompletionNotice="no" SuppressModal="yes"
AcceptEula="yes" />
<!-- <Logging Type="standard" Path="C:\Temp\"
Template="Microsoft_Access_2010_Runtime_Setup(*).log" />
<COMPANYNAME Value="Company Name" /> -->
<Setting Id="SETUP_REBOOT" Value="IfNeeded" />
</Configuration>

you can also specify a logfile location and a company name, just
uncomment the two lines.

than run setup.exe in the same folder:
setup.exe /config config.xml

stefan

Is the other half of this story that if the person running the installer takes the option to Cancel the Access 2010 Runtime install (because they already have a full version of Access, for example), the Runtime installer willalready have made (and will not reverse) changes that lose the existing Access association with .mdb files etc? This appears to be the case. Is there a way to avoid/remedy the problem? I suppose the installer for the Accessapp I distribute could check for Access before it invokes the Runtime installer; but users with older versions of Access might prefer to use the 2010Runtime for the app...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top