[AccessD] Help with Macro Security Level, Trusted Locations, Signatures et al

Jim Hewson jm.hwsn at gmail.com
Thu Jun 7 08:42:43 CDT 2012


Great! I'm glad it worked for you.
Jim
On Thu, Jun 7, 2012 at 8:36 AM, Andrew Lacey <andy at minstersystems.co.uk>wrote:

> Hi Jim
>
> Group policy mustn't be because the Addpath exe that JC pointed me to has
> worked. Thanks for advice anyway.
>
> Andy
>
>
> On 07 June 2012 at 14:26 Jim Hewson <jm.hwsn at gmail.com> wrote:
>
> > That's the point.
> > With a group policy in place Registry changes will not work.
> > Even using regedit does not work. I've tried it.
> >
> > Let me define group policy...  Group Policy is a MS feature for Windows
> 7.
> > This means the IT department can dictate what ALL users can do on their
> > machines.
> > In my case ALL macros (read code) are disabled and Trusted Locations are
> > NOT allowed.
> > With a group policy in place, changes to the visible registry are not
> > effective.
> >
> > I suggest that before you go down the primrose path... talk with the IT
> > departmart to ensure group policy is not in place.
> >
> > Jim
> > On Thu, Jun 7, 2012 at 7:52 AM, Andrew Lacey <andy at minstersystems.co.uk
> >wrote:
> >
> > > Thanks Jim, don't think I've a problem using trusted locations, as
> long as
> > > I can
> > > create one.
> > >
> > > JC, do you know what the registry update is? I've found this on-line:
> > >
> > > [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security]
> > > "VBAWarnings"=dword:00000001
> > >
> [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted
> > > Locations\Location3]
> > > "Path"="C:\Database"
> > > "Description"=""
> > > "Date"="6/7/201209 4:00 PM"
> > >
> > > but when I run the .Reg file I get the message saying "Are you sure you
> > > want to
> > > update the registry" but then it can't be imported because it's not a
> > > registry
> > > script. Any ideas?
> > >
> > > Andy
> > >
> > >
> > >
> > > On 07 June 2012 at 13:40 Jim Hewson <jm.hwsn at gmail.com> wrote:
> > >
> > > > I am a contractor for a government agency.  They have implemented
> group
> > > > policy to disable macros and trusted locations.  I've tried a
> registry
> > > hack
> > > > and all sorts of things to by-pass the messages that come up to no
> avail.
> > > > The best that I can do is to train the user what the messages mean
> and
> > > what
> > > > to do.  I've also learned that since I'm using Access 2007, if I
> change
> > > the
> > > > extension to ACCDR (runtime) only one message appears.
> > > > Jim
> > > > On Thu, Jun 7, 2012 at 5:46 AM, jwcolby <jwcolby at colbyconsulting.com
> >
> > > wrote:
> > > >
> > > > > I use a third party app which creates a trusted location.  However
> it
> > > does
> > > > > so with registry writes which may not work in your case.
> > > > >
> > > > > John W. Colby
> > > > > Colby Consulting
> > > > >
> > > > > Reality is what refuses to go away
> > > > > when you do not believe in it
> > > > >
> > > > > On 6/7/2012 4:36 AM, Andrew Lacey wrote:
> > > > >
> > > > >> Ok so you deliver a working MDB and the first thing the user sees
> when
> > > > >> they open
> > > > >> it is a series of popups warning about stopping running macros and
> > > then
> > > > >> allowing
> > > > >> them to run this one. The Medium-level Access macro security
> stuff.
> > > All
> > > > >> very
> > > > >> messy. Site won't permit setting Low security because of risk from
> > > other
> > > > >> Access
> > > > >> apps. Reading the MS literature it looks to me as if the easiest
> > > solution
> > > > >> is to
> > > > >> create a trusted location but as I plan to roll this out using
> Access
> > > 2010
> > > > >> Runtime I suspect the end-user pc's won't have the tools tto
> cereate a
> > > > >> trustred
> > > > >> location (or am I wrong?). What do you guys do? Am looking for
> > > simplest
> > > > >> solution.
> > > > >>
> > > > >> Cheers
> > > > >>
> > > > >> Andy
> > > > >>
> > > > >
> > > > > --
> > > > > AccessD mailing list
> > > > > AccessD at databaseadvisors.com
> > > > > http://databaseadvisors.com/**mailman/listinfo/accessd<
> > > http://databaseadvisors.com/mailman/listinfo/accessd>
> > > > > Website: http://www.databaseadvisors.**com<
> > > http://www.databaseadvisors.com>
> > > > >
> > > > --
> > > > 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
> > >
> > --
> > 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
>


More information about the AccessD mailing list