Re: Set Menu options

Tech-Archive recommends: Fix windows errors by optimizing your registry

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?&lang=&cr=&guid=&sloc=en-us&dg=microsoft.public.access.modulesdaovba&p=1&tid=bb95befb-994d-46b0-bf05-25e26eccfefd

does this help any?
--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)



"Stephen sjw_ost" wrote:

Thank you Jack. You and I are thinking on the same level. I don't want to to
set the macro security to low for every single macro or piece of code in
every DB or spread***. I only want it set to low on the application
macro/code that I know are trustworthy, like my own for my company.
In the interim, seeing as how the code I submitted does bring up the macro
security window, I can at least give my users the option to change it on the
DB start up.

If we can't change the setting using code, can we DETECT what the setting is
currently set to?

If this can be done, then I can set up an IF/THEN statement that would be
something like;

If MacroSecurity = LOW Then
Normal use
Else
yes/no msgbox "To use this DB you must set your security to low" include
explaination and disclaimers in the msgbox.
User answers YES -
CommandBars("Menu Bar")._
Controls("Tools")._
Controls("Macro")._
Controls("Security...")._
accDoDefaultAction
User answers NO - Docmd.Quit
End If

Just a thought...

Anyway,
If this option is truly not currently available, then does anyone know how
this can be submitted and/or suggested to microsoft to be available in a
future version, update or patch for visual basic?

Maybe a simple patch to be able to assign the macro security to publisher
XYZ like Jack mentioned.

The responsible user would initially accept or decline the publishers
security setting. If they decline then the application would close, no harm
no foul. But if the responsible user accepts, then the application would be
made available from that point on and the user would not need to make
security changes for that DB to be able to use it in it's full capacity.

Just another thought...

The big question is still: If we can't change the macro security setting
using code, can we DETECT what the setting is currently set to?

Thanks for the advice, suggestions and help.
--
Stephen


"Jack Leach" wrote:

I've often wondered if there's a way to publish your project under XYZ and
set the client computers to accept macros from publisher XYZ.

I've never really dealt with this type of stuff, but it would seem a good
way to retain security on untrusted publishers, but not have to go through
the security screens when using our own applications.

Does anyone know if this is possible?

--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)



"John W. Vinson" wrote:

On Thu, 23 Apr 2009 21:31:01 -0700, Stephen sjw_ost
<Stephensjwost@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Can this code be used to perform this function?
Or, is there any code available to set the macro security?

If there were then macro security would be absolutely useless, since it could
not be set in a way that would keep that setting.

No.
--

John W. Vinson [MVP]

.

Quantcast