Thank you for your reply! Current document protections:



Forms are set to Read-Only so that they can be filled out and printed or saved as a unique record. They're a combination of instructional paragraphs and tables holding content controls. Users can't accidentally add text to the instructional paragraphs via grouping the entire document (i.e. ctrl+A > group).

My predecessor did not use forms, just blank spaces in tables, so some of our forms cannot use filling in forms as an editing restriction. When I began updating, I looked into using Restricting Editing, and at some point discovered certain functions that I wanted did not work while it was active (I'd honestly have to go back, I can't remember specifically why). Grouping has worked well up until this point.

I tried Restricting Editing to Filling in Forms and the same VBA error comes up in attempting to execute the range.delete, as though maybe "Filling in Forms" is an existing macro to group the entire document.

What did you mean by rad-only protection? I'm not familiar with that term.

True, but that doesn't mean you can't use 'read-only' protection with the appropriate ranges marked as exceptions. In any event, you could take the opportunity to enhance what you've been given with content controls or formfields (not both in the same document).What you can do depends on what kind of editing restrictions you apply. Word's 'filling in forms' protection is more restrictive than its 'read-only' protection, but the latter doesn't work with formfields.
Typo - 'read-only' protection.

It would be a lot easier to give applicable advice if we could see the actual document. Can you attach the document to a post with some representative content (delete anything sensitive)? You do this via the paperclip symbol on the 'Go Advanced' tab at the bottom of this screen.

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