Quote:
Originally Posted by Nikko963
Thanks, except that #2 has the same problem in reverse. If I lock with exceptions, then a field within the body of the document which doesn't have an exception cannot be modified by my VB script. (Same error.) So while this might take care of my header problem, since the user can't access the header anyway, it just gives me the same problem for fields elsewhere in my document.
I need to have content control objects within the body of my document and my header whose content can only be set by my VBA script. There will naturally be other CC objects (only within the body of the doc) that the user can modify but the user shouldn't be able to touch anything else.
|
I'd have thought that's be obvious. If you apply 'No changes (read only)' protection, only ranges marked as range exceptions can be edited (whether content controls or not); and I did say:
Quote:
|
with the appropriate range exceptions
|
Solution #3 works quite happily without requiring macros or linked content controls.