Autoshapes cannot be inserted/modified when Document Protection is

[Guest]

Word 2003: We need to be able to insert/modify autoshapes, text boxes,
headers/footers when Document Protection is on. Word does not allow us to do
this, even in the editable regions of the document. Does anyone know of a way
round this?

 

[Graham Mayor]

If you need to edit the document so extensively, it might be better to use a
different type of data collection eg macrobutton fields
http://www.gmayor.com/Macrobutton.htm or userforms
http://word.mvps.org/FAQs/Userforms.htm

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP

My web site www.gmayor.com

<>>< ><<> ><<> <>>< ><<> <>>< <>><<>

 

[Guest]

Thanks but I don't believe macros & userforms are suitable for our
application. This application stores a Word document as a set of H1, H2, H3,
or H4 topics (chunks) in a database with the topic Id planted (as a bookmark)
in the topic heading. We use document protection to lock the topic heading to
prevent the bookmark from being deleted. Everything else needs to be
editable, including the graphical layer. It seems strange (if not to say a
design fault) that the graphical layer cannot be protected/unprotected in the
same way as the rest of the content.

 

[Cindy M -WordMVP-]

Hi =?Utf-8?B?U3RldmVQ?=,

Thanks but I don't believe macros & userforms are suitable for our
application. This application stores a Word document as a set of H1, H2, H3,
or H4 topics (chunks) in a database with the topic Id planted (as a bookmark)
in the topic heading. We use document protection to lock the topic heading to
prevent the bookmark from being deleted. Everything else needs to be
editable, including the graphical layer. It seems strange (if not to say a
design fault) that the graphical layer cannot be protected/unprotected in the
same way as the rest of the content.

That's simply the way graphics protection works in Word. If you have Word 2003 a
bit more of the functionality is available with the newer protection mechanism.
But the graphics layer is still locked.

It might make more sense to put the topic ID into a custom document property
and, if you need to display it, use a DocProperty field. Then the actual
information can't be deleted accidentally from the document (although the field
could be deleted, it would be easy enough to put back).

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail

 

[Guest]

Thanks Cindy. Our application is used to pull hundreds of topics together
into a single Word document. Can Custom Properties be used to store multiple
Ids? It seems to me to be designed to hold document-level info only.

 

[Cindy M -WordMVP-]

Hi =?Utf-8?B?U3RldmVQ?=,

Our application is used to pull hundreds of topics together
into a single Word document. Can Custom Properties be used to store multiple
Ids? It seems to me to be designed to hold document-level info only.

You can certainly create multiple custom properties (this is something other
than built-in document properties). I'm not sure what you mean by
"document-level info" as opposed to storing the information in bookmarks? The
stuff you put in the bookmarks isn't linked to an outside source, is it?

An alternative would be to use Word's internal document Variables (not to be
confused with programming variables) with DocVariable fields. The biggest
difference between the two is that the user has no access to doc Vars; they
have to be created and managed using the object model.

Hmmm. Another thing you could consider would be to set "Different first page"
for the headers/footers. Put the information you want to "protect" into a frame
or textbox in the header layer of the first page, so the user can't
accidentally select it.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail