FoxPro Setup - Access to system Registry denied

Author

Access to system Registry denied

Joe

2005-04-07, 8:05 pm

We have a few FoxPro programmers on staff, they currently have local admin
rights on the machine they work on, I was told to remove them from the local
admin group to they cant install apps, change settings etc., so I changed
one user just to see how things will work out, first problem I bumped into
is when the user tried to build a EXE he received a message 'Access to
system Registry denied', so is it possbile to assign specific perrmisions to
specific areas in the resigtry or file system, so they can do everything
they need to work, or do then need admin rights. They mainly use FoxPro 8.0

Thanks

Stefan Wuebbe

2005-04-07, 8:05 pm

There are roundabout two "gotchas" when working with the Vfp IDE
as a "limited" WinXP user.
Your case usually happens only when building COM server components.
IOW, the Build process should work fine for a limited user account when
building an EXE from a project without any
Define Class xy as Whatever OLEPUBLIC
involved.
If you do want to do the latter, current Win user account needs writing
privileges for HKEY_CLASSES_ROOT

The other one is that occasionally the IDE wants to write to the VFP
Home() folder, e.g. when working with the object browser, FFC examples etc.
Both cases should work after modifying the Win ACLs accordingly.

hth
-Stefan

"Joe" <me@me.com> schrieb im Newsbeitrag
news:u42bBz3GFHA.3076@tk2msftngp13.phx.gbl...
> We have a few FoxPro programmers on staff, they currently have local admin rights
> on the machine they work on, I was told to remove them from the local admin group
> to they cant install apps, change settings etc., so I changed one user just to see
> how things will work out, first problem I bumped into is when the user tried to
> build a EXE he received a message 'Access to system Registry denied', so is it
> possbile to assign specific perrmisions to specific areas in the resigtry or file
> system, so they can do everything they need to work, or do then need admin rights.
> They mainly use FoxPro 8.0
>
> Thanks
>
>

|\_/| ------ ProLib - programmers liberty -----------------
(.. ) Our MVPs and MCPs make the Fox run....
- / See us at www.prolib.de or www.AFPages.de
-----------------------------------------------------------

Dennis P. Harris

2005-04-07, 8:05 pm

On Fri, 25 Feb 2005 16:00:47 -0500 in
microsoft.public.fox.vfp.setup.environment, "Joe" <me@me.com>
wrote:

> We have a few FoxPro programmers on staff, they currently have local admin
> rights on the machine they work on, I was told to remove them from the local
> admin group to they cant install apps, change settings etc.,

what kind of pinheads do you have in management? these folks are
PROGRAMMERS, not secretaries! tell your network managers that
trying to lock down programmers' machines is a real dumb move.

Stefan Wuebbe

2005-04-07, 8:05 pm

"Dennis P. Harris" <wright.jnumgr@alaska.nospam.com> schrieb im Newsbeitrag
news:7snk21hrdmapovk
8d6ipnbc171cctk6f0s@
4ax.com...
> On Fri, 25 Feb 2005 16:00:47 -0500 in
> microsoft.public.fox.vfp.setup.environment, "Joe" <me@me.com>
> wrote:
>
>
> what kind of pinheads do you have in management? these folks are
> PROGRAMMERS, not secretaries! tell your network managers that
> trying to lock down programmers' machines is a real dumb move.

Probably a little OT, but using a "limited" Windows account for daily
work makes a lot of sense IMO.
Although I agree that even in big networks it may be useful to let
programmers have an alternative local admin account for maintenance,
setup jobs etc.

-Stefan

--
|\_/| ------ ProLib - programmers liberty -----------------
(.. ) Our MVPs and MCPs make the Fox run....
- / See us at www.prolib.de or www.AFPages.de
-----------------------------------------------------------

Sponsored Links