darren via AccessMonster.com wrote:
To set the macro security on each users PC/Access would defy their IT policy.
I believe that by opening the database with a bat file you can set the
security to low for just that instance/session. The script I have seen to do
this opens access. However, I use the FE updater and that already handles the
opening of access.
Tony's site mentions the ability of using a bat file but I believe the script
required may clash with the updaters own intended use.
I see, hmmmmm.
IN my organization, there's no "standard" setting for the macro
security, although most users come to me and want to know how to turn
the irritating start up message off. However, as far as I know, Tony's
utility doesn't open Access - it checks last modified dates on the
windows file. Now I could be wrong on this. However, I haven't had any
problems with the updater not working on the default medium (I don't
know if anyone has set it to high) security setting. That said, it
could be because no one has it at medium anymore, but given my
understanding of how Tony's excellent utility works, it shouldn't matter.
In fact, it doesn't. I just did a quick experiment to see. here's what
I did.
I changed macro security from low to medium (the MS recommended default)
and turned off all my Access apps. I then turned on the main app that
is launched by the Auto FE Updater short cut created by Tony's utility.
Since there was no new version of it on the server, it started
immediately, however, the Security warning dialog did appear. This is
the expected behaviour.
Next, I put a new copy of the front end onto the server location
specified by the Auto FE Updater shortcut, ie, the location from which
my users draw the newest FE via their own Auto FE Updater shortcuts when
I make updates to it. I then closed all my apps on my machine and
double clicked the Auto FE Updater shortcut for the app in question.
What happened was that before Access started, the new version of the FE
was copied over first, at least according to the "copying" dialog that
appears when the new FE is copied. It was only after that was finished
that the FE opened in Access and, again, I was confronted with the
security dialog.
So, my conclusion is that the Auto FE Updater shortcut will update the
front end and only pop up the security message when the Access FE is
opened. It seems to me you needn't worry about any conflicts. 8)
But the original question still remains, I guess, and that is how to
bypass the warning altogether and use the Auto FE Updater shortcut. 8)
For that you'd probably best write Tony from the web site.
--
Tim
http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Be Careful, Big Bird!" - Ditto "TIM-MAY!!" - Me