[AccessD] Writing to Registry

I only write to the registry key that VBA defaults to:
HKEY_CURRENT_USER\Software\VB and VBA Program Settings

I think (but am not positive) that when this key tree is used it is the
application's security that matters not the user's.

Anyone have any ideas on that?

I do read from other keys like HKEY_LOCAL_MACHINE\Software (and have never
had a problem) but I think the security is generally set to prevent altering
the key not reading it.

JB

-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]On Behalf Of Shamil Salakhetdinov
Sent: Thursday, February 13, 2003 10:33 AM
To: AccessD
Subject: Re: [AccessD] Writing to Registry


> or would that just apply to HKEY_CURRENT_USER
> - I write to HKEY_LOCAL_MACHINE
Richard,

I've had a situation (NT4) when end-users were disallowed to write into
System Registry.
HKEY_LOCAL_MACHINE was blocked for them for writing/deleting.
AFAIS this can be done via Domain Security Policy(W2K) for all the keys of

HKEY_CLASSES_ROOT,
HKEY_LOCAL_MACHINE and
HKEY_USERS

Or even for a certain system registry key.

It doesn't look like it's possible to block HKEY_CURRENT_USER and
HKEY_CURRENT_CONFIG.
But I've never did that no manually, no programmatically so I can be wrong.

Does anybody know that for sure? - I mean if HKEY_CURRENT_USER can't be
blocked then it should never(?) be the source of the problems of writing
custom entries under this registry key...

Shamil

----- Original Message -----
From: "Griffiths, Richard" <R.Griffiths at bury.gov.uk>
To: <accessd at databaseadvisors.com>
Sent: Thursday, February 13, 2003 6:34 PM
Subject: RE: [AccessD] Writing to Registry


> Seth
> thanks, my concerns were over permissions say on a network/ NT  where
users
> may be restricted in writing to and from the registry (or would that just
> apply to HKEY_CURRENT_USER - I write to HKEY_LOCAL_MACHINE (I already have
> some code, more is always welcome)
> thanks
> Richard
>
> > -----Original Message-----
> > From: Seth Galitzer [SMTP:sgsax at ksu.edu]
> > Sent: 13 February 2003 15:15
> > To: accessd
> > Subject: Re: [AccessD] Writing to Registry
> >
> > Richard,
> >
> > No problem at all.  There are some of built-in registry read/write
> > functions, but they are not very flexible.  I have a module that
> > contains code for reading and writing anywhere from the registry.  I can
> > post it here or send it offline if you like.
> >
> > The path to msaccess.exe is already stored in the registry in here:
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
> > Paths\MSACCESS.EXE
> >
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths
> >
> > contains subkeys which list the paths to most of your installed
> > software.
> >
> > Seth
> >
> >
> > On Thu, 2003-02-13 at 03:13, Griffiths, Richard wrote:
> > > Hi Group
> > >
> > > I now store some details about my application in the local settings of
> > the
> > > registry (eg MSAccess.exe folder and data folder location) - anyone
> > foresee
> > > problems with this?
> > >
> > > Richard
> >
> > --
> > Seth Galitzer sgsax at ksu.edu
> > Computing Specialist http://puma.agron.ksu.edu/~sgsax
> > Dept. of Plant Pathology
> > Kansas State University
> >
> > _______________________________________________
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> --------------------------------------------------------------------------
------------------------------------------
> This e-mail, together with any files transmitted with it, is
> confidential and intended solely for the use of the individual to
> whom it is addressed. If you are not the intended recipient, or
> the person responsible for delivering to the intended recipient,
> be advised that you have received this e-mail in error and that any
> use, dissemination, forwarding, printing or copying of this e-mail
> is strictly prohibited without liability on our part.
>
> If you have received this e-mail in error please notify the sender.
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com