Access program from regular account

7 Oct 2005 2:56 PM

Wyne

Hello,

I have an App made using VB6. One of our customers installed it on a XP
(professional) machine from the Admin account and run it from the Admin
account, every thing was OK. But when he logged on as a regular user, the
program keeps showing error message, saying that some access is not allowed.

I doubt it is related to Registry access restriction. This App uses Registry
to store some configuration data.

How can I modify the App to let it run from regular account? Or, how can I
change the machine's setting so that this specific program is fully
functional via a specific user account?

Thanks in advance.

7 Oct 2005 3:19 PM

MikeD

"Wyne" <W***@discussions.microsoft.com> wrote in message
news:C57355E9-AB60-4DD1-AE94-679BE0944467@microsoft.com...
> Hello,
>
> I have an App made using VB6. One of our customers installed it on a XP
> (professional) machine from the Admin account and run it from the Admin
> account, every thing was OK. But when he logged on as a regular user, the
> program keeps showing error message, saying that some access is not
> allowed.
>
> I doubt it is related to Registry access restriction. This App uses
> Registry
> to store some configuration data.

You mean you DO think it's related to the Registry? That's very possible.
Regular User accounts have very restricted Registry access. Where are you
saving this configuration data? If it happens to be anything under
HKEY_LOCAL_MACHINE, regular User accounts can read this, but can't change it
(because they don't have write permissions).

>
> How can I modify the App to let it run from regular account? Or, how can I
> change the machine's setting so that this specific program is fully
> functional via a specific user account?

You have to write your app "correctly". For example, if you need to create
or modify settings in the Registry, these must be under HKEY_CURRENT_USER.
As a rule, you shouldn't change permissions as that compromises security
(and I know of no sysadmin that would allow it anyway).

It's pretty hard to give you any detailed help since you were pretty vague
about everything in your post. You need to provide some specifics.

--
Mike
Microsoft MVP Visual Basic

7 Oct 2005 7:27 PM

Brian

By regular... you mean "limited" user?

I concur with Mike that it is probably registry issues... create a seperate
registry for HKEY_CURRENT_USER and store app specific (read/write) data
under that location. You can still store "Read Only" data under the
HKEY_LOCAL_MACHINE location.

There are several example projects and classes for reading and writing to
the registry.

Brian

Show quoteHide quote

"MikeD" <nob***@nowhere.edu> wrote in message
news:#6VY9J1yFHA.3180@TK2MSFTNGP14.phx.gbl...
>
> "Wyne" <W***@discussions.microsoft.com> wrote in message
> news:C57355E9-AB60-4DD1-AE94-679BE0944467@microsoft.com...
> > Hello,
> >
> > I have an App made using VB6. One of our customers installed it on a XP
> > (professional) machine from the Admin account and run it from the Admin
> > account, every thing was OK. But when he logged on as a regular user,
the
> > program keeps showing error message, saying that some access is not
> > allowed.
> >
> > I doubt it is related to Registry access restriction. This App uses
> > Registry
> > to store some configuration data.
>
> You mean you DO think it's related to the Registry? That's very possible.
> Regular User accounts have very restricted Registry access. Where are you
> saving this configuration data? If it happens to be anything under
> HKEY_LOCAL_MACHINE, regular User accounts can read this, but can't change
it
> (because they don't have write permissions).
>
> >
> > How can I modify the App to let it run from regular account? Or, how can
I
> > change the machine's setting so that this specific program is fully
> > functional via a specific user account?
>
>
> You have to write your app "correctly". For example, if you need to
create
> or modify settings in the Registry, these must be under HKEY_CURRENT_USER.
> As a rule, you shouldn't change permissions as that compromises security
> (and I know of no sysadmin that would allow it anyway).
>
> It's pretty hard to give you any detailed help since you were pretty vague
> about everything in your post. You need to provide some specifics.
>
> --
> Mike
> Microsoft MVP Visual Basic
>
>