Protect/Unprotect form document

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Keith - 20 May 2004 21:33 GMT

I have Word 2002 at work. When working in a form
document, I can protect/unprotect (lock/unlock) the
document with no change to the data entered in the form
fields.

At home, I have Word 2000. When I unlock/lock a form
document, it clears all the data I have entered in the
form fields.

Is there a switch somewhere in 2000 to turn this off? I
want to be able to switch back and forth between
protected/unprotected as necessary without losing my
already inputted data.

TIA
Keith

Reply to this Message

Charles Kenyon - 20 May 2004 22:56 GMT

In Word 2000 and earlier, there is no switch. You need to build a macro to
do it. You can find instructions at
http://word.mvps.org/FAQs/MacrosVBA/TurnFmFlfResetOff.htm

What you are talking about is what Word calls an "online form." Check this
in help. For more about online forms, follow the links at
http://addbalance.com/word/wordwebresources.htm#Forms or
http://word.mvps.org/FAQs/Customization/FillinTheBlanks.htm especially Dian
Chapman's series of articles.

Hope this helps,

Signature

Charles Kenyon

Word New User FAQ & Web Directory: http://addbalance.com/word

Intermediate User's Guide to Microsoft Word (supplemented version of
Microsoft's Legal Users' Guide) http://addbalance.com/usersguide

See also the MVP FAQ: http://www.mvps.org/word which is awesome!
--------- --------- --------- --------- --------- ---------
This message is posted to a newsgroup. Please post replies
and questions to the newsgroup so that others can learn
from my ignorance and your wisdom.

> I have Word 2002 at work. When working in a form
> document, I can protect/unprotect (lock/unlock) the
[quoted text clipped - 12 lines]
> TIA
> Keith

Reply to this Message

Keith - 24 May 2004 18:46 GMT

Thanks! I'll start digging and hacking.

>-----Original Message-----
>In Word 2000 and earlier, there is no switch. You need to build a macro to
[quoted text clipped - 26 lines]
>
>.

Reply to this Message