O
Oleg Krupnov
Hi,
I have added a standard ActiveX control (e.g. CommandButton) from the Word's
Control Toolbox and saved the document. The next time I open the document, I
see the macro security warning (my security level is set to medium).
1) Is this by design, even though the ActiveX is supplied by Microsoft,
present in ALL copies of Word and therefore should be trusted? Should
additional action be taken to trust even these controls?
2) I used to think that as soon as an ActiveX control had been installed on
a machine, it means that the user had trusted it and the security warning
should no longer appear. It should appear only for ActiveX controls DEFINED
inside the VBA project of the document being opened. Am I wrong? What is the
reasoning?
3) How do I workaround to avoid my users from seeing this warning? Consider
the following scenario: I have developed a VSTO customization based on a Word
DOT template. The .NET code creates a standard CommandBar ActiveX control
inside the document at run time, with no VBA code attached to it. Then the
document is saved and then reopened by the same/other user. What should I do
to prevent the macro security warning?
Thanks
I have added a standard ActiveX control (e.g. CommandButton) from the Word's
Control Toolbox and saved the document. The next time I open the document, I
see the macro security warning (my security level is set to medium).
1) Is this by design, even though the ActiveX is supplied by Microsoft,
present in ALL copies of Word and therefore should be trusted? Should
additional action be taken to trust even these controls?
2) I used to think that as soon as an ActiveX control had been installed on
a machine, it means that the user had trusted it and the security warning
should no longer appear. It should appear only for ActiveX controls DEFINED
inside the VBA project of the document being opened. Am I wrong? What is the
reasoning?
3) How do I workaround to avoid my users from seeing this warning? Consider
the following scenario: I have developed a VSTO customization based on a Word
DOT template. The .NET code creates a standard CommandBar ActiveX control
inside the document at run time, with no VBA code attached to it. Then the
document is saved and then reopened by the same/other user. What should I do
to prevent the macro security warning?
Thanks