If you don't want people to change it, what use is a FillIn field? Better
would be to use a DocProperty or DocVariable field, with the branch-specific
information stored in one or more DocumentProperties or DocumentVariables.
However, there is no way to lock down the footer to stop people changing it.
It's just as effective, in practice, simply to ask people leave the footer
alone. Most users will do as asked, and those that won't will make a point
of defeating your 'lock down'.
There is no locking down or protection you can apply that any experienced
user can't quickly get around. All you do is annoy the inexperienced users.
And worse, *you* get held responsible for everything that goes wrong with
people's Word usage: you'll find yourself fielding calls from users telling
you that ever since you installed your screwy template, their copy of Word
has stopped working properly, they keep losing documents, etc, etc.
kimc said:
This is a custom memo template for a client. They want the footer to be
different for each office that uses it and this template will be on the
company website, so it needs to be generic. They are trying to lock down
the form so changes aren't made so that's why I can't just put plain text in
the footer for people to make changes to it.
