Search | Active Topics



Using Startaccess3_2003.exe in Windows XP with Power Users Options
MichaelF
Posted: Tuesday, May 04, 2010 10:18:00 AM
Rank: Member
Groups: Member

Joined: 1/19/2010
Posts: 18
Location: United Kingdom
We are encountering an issue when attempting to deploy startaccess3_2003.exe in a corporate environment. The workstations are running Windows XP and Office 2007. Our application installs the Access 2003 runtime (not using the Sagekey Access Deployment Wizard). Application users are limited to the Power Users local security group. After a network administrator installs the Access 2003 Service Pack 3 (using their own account), the application users are constantly confronted with the Office reconfiguration wizard when switching between our application and Access 2007. In this environment it is not feasible to temporarily elevate the user accounts to Local Administrator during the SP3 install. Can you suggest a work-around to this problem? Thanks.
ColeS
Posted: Tuesday, May 04, 2010 10:34:09 AM

Rank: SageKey Staff
Groups: Administration , Member

Joined: 3/27/2009
Posts: 1,376
Location: Canada
Hi Michael,

When the Access Deployment Wizard installs the Runtime, it runs a couple commands through StartAccess to open the required permissions on the registry. When not using the Wizard to load the runtime, these are the commands you can use:

Run StartAccess3_2003.exe -capture

Install the Access Runtime

Run StartAccess3_2003.exe -openkeys

Run StartAccess3_2003.exe -restore


If the Runtime is already installed then you can simply run the -openkeys command with StartAccess. This should open the permissions you need for StartAccess to protect against the reconfiguration message. You may see the reconfiguration once or twice more as the values get properly set.

What program are you using to install the application? Are you creating custom shortcuts like the Wizard does that point to StartAccess?
MichaelF
Posted: Tuesday, May 04, 2010 1:06:07 PM
Rank: Member
Groups: Member

Joined: 1/19/2010
Posts: 18
Location: United Kingdom
Hi Cole,
Our installation script already includes the sequence of commands you listed. The Access 2003 runtime is pre-installed. We are not clear on how exactly –openkeys works:
1) Is it correct to assume that the scope of –openkeys is user-specific (HKCU vs. HKLM )?
2) Does a member of the Power Users group have permissions to execute –openkeys?
3) Would there be any adverse effect to leaving the –openkeys parameter permanently on the command line?

In reply to your questions, we use Wise Installbuilder to install the application. Our custom application loader has been modified to include Startaccess3_2003.exe to launch Access. We do not use the –cmd option of Startaccess because our loader builds the command line dynamically.

Thanks,
Michael
ColeS
Posted: Tuesday, May 04, 2010 3:05:26 PM

Rank: SageKey Staff
Groups: Administration , Member

Joined: 3/27/2009
Posts: 1,376
Location: Canada

StartAccess3_2003.exe -openkeys is run for HKLM.

It does not run for Power Users, it requires an admin.

If -openkeys is in the command line it will only try to open the keys in the registry and not continue on to run the application.
Users browsing this topic
Guest


Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Main Forum RSS : RSS

Forum theme created by Colin Olson, SageKey Software.
Powered by Yet Another Forum.net version 1.9.1.8 (NET v4.0) - 3/29/2008
Copyright © 2003-2008 Yet Another Forum.net. All rights reserved.
This page was generated in 0.040 seconds.