Protecting Header When Merging

[Steve]

I've got the problem of needing to furnish a Letterhead
document for about 2000 users in over 50 locations. The
Header info must remain unchanged while allowing the
customization of their individual information (Phone,
address) in the footer AND allowing them to use the
letterhead as a merge document. How can I proceed?

 

[darin]

create a section break after the header and protect only the first section.

 

[Jezebel]

There's no way to *force* the users here. Forget the idea of a form with
locked sections. Your users will end up with a document they can't use
properly. And with 2000 users, that's a LOT of service calls to field.

Create a template containing the header as you want it, and with dummy
information in the footer. Distribute that with a set of instructions for
customising it, and a polite request that they leave the header unmodified.