Hi webharvest,

So why are the users allowed to edit things like the Proposal Name other than through the userform? Bookmarks are fragile. So, instead of using bookmarks, I'd suggest having your code maintain/update custom document properties with the data and use DOCPROPERTY fields where required to replicate the data.

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Well my initial thought was I would just use the userform to make the creation of the document easier and then let the person edit the document as normal after the initial creation. I initially thought this way because the people doing this work are not very computer savvy and I figured I would get less resistance.

When you say docproperties do you mean document variables? If so I am using them in some places of the userform.

Okay so lets say I do only allow the person to change these variables via the userform; I have a couple questions
1) Right now I only call up the userform when a new document is created from the template. What is a clean way to have the userform pop back up when the user wants to change something? I thought about a macro button but we have to print or make pdfs to send out to people and I don't want the button to show up in the final document.
2) What is the right way to lock down all the docvariables and/or book marks but still let the user modify the rest of the document? There is a lot of text that needs to be document specific so I have to let the user change some things.

Thanks