>I resolved both issues: they were due to the macro security level being set
> to high. Now I have a new question. How can I resolve that issue on all
> PCs
> throughout the network?
You need either to get all users to reduce their macro security level to
medium, or you need to sign the template with a digital certificate, so that
it can be trusted on systems that are set to High security.
You can create your own certificate using the Selfcert.exe utility that
comes with a full installation of Office 2003.

Signature
Regards
Jonathan West - Word MVP
www.intelligentdocuments.co.uk
Please reply to the newsgroup
Keep your VBA code safe, sign the ClassicVB petition www.classicvb.org
JeannetteH - 30 Apr 2007 18:38 GMT
Thank you Jonathan, that is very helpful. Trying to get hundreds of people
to conform is difficult.
> >I resolved both issues: they were due to the macro security level being set
> > to high. Now I have a new question. How can I resolve that issue on all
[quoted text clipped - 7 lines]
> You can create your own certificate using the Selfcert.exe utility that
> comes with a full installation of Office 2003.
Macro security settings.
Read this article to get a good understanding of Office 2003 security
settings in an enterprise setting
http://www.microsoft.com/technet/prodtechnol/office/office2003/operate/o3secdet.mspx
--
Krgrds,
Perry
System:
Vista/Office Ultimate
VS2005/VSTO2005 SE
>I resolved both issues: they were due to the macro security level being set
> to high. Now I have a new question. How can I resolve that issue on all
[quoted text clipped - 23 lines]
>>
>> Any suggestions would be greatly appreciated.
JeannetteH - 30 Apr 2007 20:08 GMT
Thank you Perry for the information. I will review it, I am sure it will be
a great help.
> Macro security settings.
>
[quoted text clipped - 37 lines]
> >>
> >> Any suggestions would be greatly appreciated.