T
Thomas Osthege
Hi NG,
I developed some VBA macros that run with Word 97, 2000 and 2002. They
are located in the startup folder as .dot files. All macros contain a
signature (certificate) to avoid problems at the customers site.
Normally the customer trusts my certificate, sets the corresponding
options and everything is working fine, independant of the security
options.
Now there is a customer with correctly adjusted options, but at each
startup of word the message '... contains macros. Macros can contain
virusses ...' appears (translated from German). He has to acknowledge
this by clicking on the 'Activate macros' button. With another customer
of him exactly the same problem occurs. He installed his computers, what
makes me think that it has something to do with an option that prevents
the execution of this macro. But which?
Security options:
Security level High or Medium (doesn't matter)
Trustworthy source registered (my certificate)
Trust all installed add ins and templates marked
Trust access to vb project marked
Translated from German, the english terms may sound different.
With exactly the same options it's running fine with other customers.
All files double checked.
Does anybody have an idea? I can't expect the customer to switch to low
security level.
TIA and have a nice day
Thomas
Thomas(at)Osthege(dot)de
I developed some VBA macros that run with Word 97, 2000 and 2002. They
are located in the startup folder as .dot files. All macros contain a
signature (certificate) to avoid problems at the customers site.
Normally the customer trusts my certificate, sets the corresponding
options and everything is working fine, independant of the security
options.
Now there is a customer with correctly adjusted options, but at each
startup of word the message '... contains macros. Macros can contain
virusses ...' appears (translated from German). He has to acknowledge
this by clicking on the 'Activate macros' button. With another customer
of him exactly the same problem occurs. He installed his computers, what
makes me think that it has something to do with an option that prevents
the execution of this macro. But which?
Security options:
Security level High or Medium (doesn't matter)
Trustworthy source registered (my certificate)
Trust all installed add ins and templates marked
Trust access to vb project marked
Translated from German, the english terms may sound different.
With exactly the same options it's running fine with other customers.
All files double checked.
Does anybody have an idea? I can't expect the customer to switch to low
security level.
TIA and have a nice day
Thomas
Thomas(at)Osthege(dot)de