atw: Trouble with macros

Hi,

One of my colleagues set up a macro in a template to carry out a routine
function on a batch of forms to be updated. 

The function was for form development rather than form use so the macro
only had a short useful life. 

All the forms based on the template opened with a macro warning and were
found to have the macro from the template embedded in them. 

I deleted the macro from the template and all the recent batch of forms
based on the template.

Still, all the documents based on the template open with a macro warning
even though there are no macros in them.

Since removing the macro from the template, all documents subsequently
created with the template still open with a macro warning.

What to do?

PS Have checked MS KB but might not be asking the right question ...

IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to be 
read or used by the named addressee. It is confidential and may contain legally 
privileged information. No confidentiality or privilege is waived or lost by 
any mistaken transmission to you. The RTA is not responsible for any 
unauthorised alterations to this e-mail or attachment to it. Views expressed in 
this message are those of the individual sender, and are not necessarily the 
views of the RTA. If you receive this e-mail in error, please immediately 
delete it from your system and notify the sender. You must not disclose, copy 
or use any part of this e-mail if you are not the intended recipient.
**************************************************
To post a message to austechwriter, send the message to 
austechwriter@xxxxxxxxxxxxxx

To subscribe to austechwriter, send a message to 
austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject field.

To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with 
"unsubscribe" in the Subject field.

To search the austechwriter archives, go to 
www.freelists.org/archives/austechwriter

To contact the list administrator, send a message to 
austechwriter-admins@xxxxxxxxxxxxx
**************************************************

Other related posts: