Header Row in form table doesn't work when locking sections

[floresra]

Our template Nazi is creating forms and locking some sections of the table.
He said he has to do this in order for the check boxes to toggle, but I think
it is so text can't be changed in some of the cells. We have be able to add
rows for text entry so not all the rows are locked. As a result the header
row doe not carry over if add enough rows to make the document longer than
one page.

How can you have check boxes toggle, lock cells AND keep the table header row?

 

[Graham Mayor]

If the issue only concerns check boxes, see
http://www.gmayor.com/Macrobutton.htm

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


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

 

[Suzanne S. Barnhill]

Your "template Nazi" is correct in that forms will not function as designed
unless protected. Although you will be unable to add rows to a protected
form without a macro, you can certainly get the heading row to repeat just
by marking it as a heading row; tell the template designer that he needs to
do this.

If this still doesn't provide enough flexibility, you can follow Graham's
suggestion to use a MacroButton check box instead, but be aware that this
will require enabling macros for the template (and it must be a template,
not just a document, as it has to store AutoText entries).

 

[floresra]

In addition to check boxes some of the rows are locked but some are not so
you can add rows. I was told that to have some rows locked and allowing added
others the table is broken into sections, which is the same as splitting a
table and that is why the header row doesn't carry over (like when you split
a table). Can you protect some rows but not others in a table for a protected
form and still have a header row?

 

[Suzanne S. Barnhill]

No, if you are inserting section breaks in order to leave some sections
unprotected, you are breaking the table, and the heading row will not
repeat. But (depending on layout) possibly the heading row could be inserted
in the page header instead.