Setting Macro Security=Low?

[(PeteCresswell)]

MS Access app running on a Citrix server.

Pops 3 annoying (SandBox-mode-related?) security dialogs every
time somebody opens the app.

Read a couple of MS papers on it.

Sounds like the Good-Right-And-Holy-Path is to create some kind
of "Certificate".

Not gonna happen around here.

Every ref I read explicitly said not to set security to "Low" to
get around said dialogs.

Meanwhile, the guys in charge of the dev server just set Tools |
Macro | Security | Security Level = Low and, of course, all three
dialogs went away.

The rationale is that the server is behind a firewall and
security's not an issue.

Sounds plausible to me, but I'm generally overwhelmed by the
volume of stuff that I think I know something about but really
don't have a clue about.

Are they missing anything with the Security=Low approach?

 

[Jellifish]

It's the first thing I change too. I cannot see the point of it at all.

 

[huangda 晋江兴达机械]

All you are doing is setting it to the same security that every version
of Access prior to 2003 had. Did that ever give you (or anyone else) any
problems? It certainly never caused me any grief.

It is the first thing I tell users of 2003 to change when they ask about
those dialogs.

 

[David W. Fenton]

Meanwhile, the guys in charge of the dev server just set Tools |
Macro | Security | Security Level = Low and, of course, all three
dialogs went away.

The rationale is that the server is behind a firewall and
security's not an issue.

This shows that those people really don't understand security at any
level.

I don't believe there's any significant risk of Access databases
being exploited as vectors for nefarious activity, but just because
I don't see it as a significant risk doesn't mean I don't recognize
that it's theoretically possible. MS's nags in Office 2003 are quite
annoying and seem to me to reflect the interests of corporate IT
departments that want to make it too annoying for their users to do
any significant programming. This is, I think, reflected in the work
done in A2007 to make macros more robust, so that macros can replace
code.

This is, of course, a bloody stupid course of action, as anyone who
thinks about it for a moment will recognize.

 

[(PeteCresswell)]

After reading these replies and thinking about it a little, I've
got to wonder if MS' legal department was involved in the
decisions on how/when to pop those warning dialogs.