Access Runtime on Vista Standard User?

[cabrenner]

I have an application that uses the Access 2002 Runtime. Installation
on Vista under an admin account works OK. But running the app under a
standard user account brings up the warning dialog asking to OK the
Access runtime executable, and requiring an admin password. How can
this be avoided?

TIA,

Cheryl

 

[Todos Menos [MSFT]]

I'd reccomend trying it on Access 2003 runtime before spending 5
minutes worrying about it

I just setup Quicken 2000 on my dad's new Vista box.. it worked like a
charm
I guess that it was easier-- back then-- to write portable apps..

now we're stuck with all this .NET _CRAP_ and Microsoft doesn't give a
crap about backwards compatibility any longer

 

[Graham Mandeno]

Hi Cheryl

Are you launching the app with a shortcut? Does the shortcut have the "Run
as Administrator" option specified?

 

[cabrenner]

Hi Cheryl

Are you launching the app with a shortcut? Does the shortcut have the "Run
as Administrator" option specified?

--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

I have an application that uses the Access 2002 Runtime. Installation
on Vista under an admin account works OK. But running the app under a
standard user account brings up the warning dialog asking to OK the
Access runtime executable, and requiring an admin password. How can
this be avoided?

Cheryl- Hide quoted text -

- Show quoted text -

Hi Graham,

Yes, I tried setting "Run as Administrator" on the shortcut, but it
still asks for the admin password if a standard user is logged on.

 

[Graham Mandeno]

Hi Cheryl

Yes, I tried setting "Run as Administrator" on the shortcut, but it
still asks for the admin password if a standard user is logged on.

Sorry, you misunderstood me. The shortcut should NOT be "Run as
Administrator". A shortcut with this setting needs to ask a non-admin user
for some admin credentials. Have you tried it without that option set?

 

[cabrenner]

Hi Cheryl

Yes, I tried setting "Run as Administrator" on the shortcut, but it
still asks for the admin password if a standard user is logged on.

Sorry, you misunderstood me. The shortcut should NOT be "Run as
Administrator". A shortcut with this setting needs to ask a non-admin user
for some admin credentials. Have you tried it without that option set?
--
Good Luck

Graham Mandeno [AccessMVP]
Auckland, New Zealand

Graham,

The "Run as Administrator" designation is put there by default when
the application is installed. I can't seem to find a way to get rid
of it. I have gone into the properties of the shortcut, and of the
runaccess.exe, made sure that "Run as Administrator" is not checked.
But the shield designation is still on the shortcut, and when the app
is run, the dialog box comes up saying the runaccess.exe is
"unidentified", and asks for admin password to continue.

Any suggestions?

Thanks.

Cheryl

 

[Graham Mandeno]

Sorry, Cheryl, I missed your reply

It appears that the application is installed with the SageKey Access
Run-time script, is this right? I think runaccess.exe is the "launcher"
distributed by SageKey.

You could try creating another shortcut and copy and paste the target
command line from the "Run as Admin" shortcut to your new one. I can see no
necessity for runaccess.exe to run with admin privileges.
--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

Hi Cheryl

Yes, I tried setting "Run as Administrator" on the shortcut, but it
still asks for the admin password if a standard user is logged on.

Sorry, you misunderstood me. The shortcut should NOT be "Run as
Administrator". A shortcut with this setting needs to ask a non-admin
user
for some admin credentials. Have you tried it without that option set?
--
Good Luck

Graham Mandeno [AccessMVP]
Auckland, New Zealand

Graham,

The "Run as Administrator" designation is put there by default when
the application is installed. I can't seem to find a way to get rid
of it. I have gone into the properties of the shortcut, and of the
runaccess.exe, made sure that "Run as Administrator" is not checked.
But the shield designation is still on the shortcut, and when the app
is run, the dialog box comes up saying the runaccess.exe is
"unidentified", and asks for admin password to continue.

Any suggestions?

Thanks.

Cheryl

 

[cabrenner]

Sorry, Cheryl, I missed your reply

It appears that the application is installed with the SageKeyAccess
Run-time script, is this right? I think runaccess.exe is the "launcher"
distributed by SageKey.

You could try creating another shortcut and copy and paste the target
command line from the "Run as Admin" shortcut to your new one. I can see no
necessity for runaccess.exe to run with admin privileges.
--
Good Luck

Graham Mandeno [AccessMVP]
Auckland, New Zealand

The "Run as Administrator" designation is put there by default when
the application is installed. I can't seem to find a way to get rid
of it. I have gone into the properties of the shortcut, and of the
runaccess.exe, made sure that "Run as Administrator" is not checked.
But the shield designation is still on the shortcut, and when the app
is run, the dialog box comes up saying the runaccess.exe is
"unidentified", and asks for admin password to continue.

Any suggestions?

Cheryl- Hide quoted text -

- Show quoted text -

Graham,

Thanks for your reply. Here is where I am at.

I tried creating a new shortcut, cut and pasted the target command
line from the previous shortcut, but once saved, the new shortcut also
shows the "Run as Administrator" shield. I was however able to bypass
the UAC prompt by creating a manifest file in the same directory, with
the designation to run "asInvoker".

This has allowed my appliction to start up without any prompts.
However I now get a message that states "You do not have permission to
make the requested system configuration changes. Rerun using an
administrator account." However, the application will still open and
appears to run OK - extensive testing not done yet, but basic
functionality is there.

I thought that it may be related to something in my application that
makes a registry change, even though I had already given the standard
user full control of the key. I commented out this code, yet still
received the message. After some investigation, it appears that this
message is related to the runaccess.exe, and not to my app. Change
the shortcut to point to msaccess.exe rather than runaccess.exe, and
this message no longer appears. If I change the manifest file for the
runaccess.exe to "requireAdministrator", then I get the UAC prompt,
but no message indicating that I do not have permissions.

Still looking for a solution, but I appreciate all of your
suggestions.

Cheryl

 

[Graham Mandeno]

Hi Cheryl

The problem here appears to be with the SageKey launcher, not with Access
itself.

You could try bypassing the launcher entirely. Find out where SageKey has
installed msaccess.exe and then create a new shortcut, replacing:
"C:\ ...\runaccess.exe"
with:
"C:\...\msaccess.exe"

Also, what version of Access are you using?