Quote:
Originally Posted by MGerhard
As far as I know now the basic idea behind the grouping of content controls is to ensure the content controls shall not be deleted or changed.
|
Grouping content controls has nothing to do with preventing their deletion, since it's quite easy to delete the entire group in one go. What you need for that is to set their 'cannot be deleted' property.
Quote:
|
My major problem was that while the content controls are protected through those groups the fields.update() could not update the enclosed controls.[
|
.Fields.Update has nothing to do with content controls - it applies to fields, which may contain or be contained within content controls.
Quote:
|
The last 10% would be, if I were able to recreate exact the same groups as there were before. I tried that with writing the ranges of the groups into a collection.
|
That's largely why I suggested attaching a document to a post. In any event, you don't need to provide a restricted document - only one that demonstrates the issue.