hallo!
I have some Excel 2003 SP3 procedures opening .xls files, each of them
containing VBA macros. In order to provide the highest system protection,
each time Excel requires repeatedly user permission to open, which is
tedious
and in sometimes problematic.
I wonder if there is a way to bypass this process, by notifying excel that
those specific files are safe (by file names o author).
Otherwise I'm obliged to keep the protection level to "low", but in such a
case my sistem will be exposed to damage risk from other "unknown" macros.

thanks for reply

Try self-certifying those workbook.

See
http://www.vbaexpress.com/forum/show...ht=SELCERT.EXE
--
---
HTH

Bob


(there's no email, no snail mail, but somewhere should be gmail in my addy)



"Romolo" wrote in message
...
hallo!
I have some Excel 2003 SP3 procedures opening .xls files, each of them
containing VBA macros. In order to provide the highest system protection,
each time Excel requires repeatedly user permission to open, which is
tedious
and in sometimes problematic.
I wonder if there is a way to bypass this process, by notifying excel that
those specific files are safe (by file names o author).
Otherwise I'm obliged to keep the protection level to "low", but in such a
case my sistem will be exposed to damage risk from other "unknown" macros.

thanks for reply

Thanks a lot, Bob
--
grazie, Romolo


"Bob Phillips" wrote:

Try self-certifying those workbook.

See
http://www.vbaexpress.com/forum/show...ht=SELCERT.EXE
--
---
HTH

Bob


(there's no email, no snail mail, but somewhere should be gmail in my addy)



"Romolo" wrote in message
...
hallo!
I have some Excel 2003 SP3 procedures opening .xls files, each of them
containing VBA macros. In order to provide the highest system protection,
each time Excel requires repeatedly user permission to open, which is
tedious
and in sometimes problematic.
I wonder if there is a way to bypass this process, by notifying excel that
those specific files are safe (by file names o author).
Otherwise I'm obliged to keep the protection level to "low", but in such a
case my sistem will be exposed to damage risk from other "unknown" macros.

thanks for reply

An Excel VBA procedure should be able to open a workbook that contains code,
without the macro warning. Having already approved opening of the workbook
with the VBA, or writing fresh VBA, provides implicit acceptance of the
macros in the unopened workbook.

The warning that's harder to avoid is a prompt to update any links in the
workbook being opened.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
Peltier Technical Services, Inc. - http://PeltierTech.com
_______


"Romolo" wrote in message
...
hallo!
I have some Excel 2003 SP3 procedures opening .xls files, each of them
containing VBA macros. In order to provide the highest system protection,
each time Excel requires repeatedly user permission to open, which is
tedious
and in sometimes problematic.
I wonder if there is a way to bypass this process, by notifying excel that
those specific files are safe (by file names o author).
Otherwise I'm obliged to keep the protection level to "low", but in such a
case my sistem will be exposed to damage risk from other "unknown" macros.

thanks for reply