I've created a new online form. It works perfectly for me and for most
users, but some users are unable to save the form--they get a message that
says their macro security setting prevents them from saving it. However, no
matter what they change their setting to, they still can't save the form.

The form is a .dot, if that makes any difference. And I and most of my
colleagues have no problem saving it as a .doc.

Is there an easy fix for this that I can convey when I send out the form, or
are my users going to have to call our IT department every time this happens?

Thanks!

Did they check their Macro security settings?

What version are they using...are you using?

You might want to consider creating a digital certificate using
selfcert.exe (it's on your system if you installed it...search for it
under Office) and then apply that to the template code so they don't
get macro warnings once they install your cert.

See this TechTrax article for more info...

Using SelfCert to Create Digital Certificates in a Network Environment
http://pubs.logicalexpressions.com/P...cle.asp?ID=194

Might want to also check out these articles...

Sharing Macros
http://pubs.logicalexpressions.com/P...cle.asp?ID=166

Word AutoForm Articles
http://www.mousetrax.com/techpage.html#autoforms

Dian D. Chapman
Technical Consultant, Microsoft MVP
MOS Certified, Editor/TechTrax

View Hurricane Humane Updates: http://www.mousetrax.com/pets.html
Free Microsoft Tutorials: http://www.mousetrax.com/techtrax
Learn VBA the easy way: http://www.mousetrax.com/techcourses.html





On Mon, 7 Nov 2005 14:05:02 -0800, "ErinBell29"
wrote:

I've created a new online form. It works perfectly for me and for most
users, but some users are unable to save the form--they get a message that
says their macro security setting prevents them from saving it. However, no
matter what they change their setting to, they still can't save the form.

The form is a .dot, if that makes any difference. And I and most of my
colleagues have no problem saving it as a .doc.

Is there an easy fix for this that I can convey when I send out the form, or
are my users going to have to call our IT department every time this happens?

Thanks!