Office 2010 Activation Protect Me

Tristan again – in my first post, I tried to give a really brief overview of the new content control functionality in Word 2007. In that post I had a list of the different aspects of what we did that excite me,Office 2007 Download, and in the next few posts, I'm going to dig into each of the things I talked about, why we did them, and why I think they're so exciting.
The first thing I'm going to talk about are the ways in which content controls allow you to restrict what can be done to different parts of a Word 2007 document.
Protecting the Legal Clause
In that previous post, I showed you the example of a legal clause at the end of a document, and how I wanted to make sure that none of the people that edit that document accidentally delete it,Windows 7, but I didn't explain how I made that work.
Let's start there. Here's the document:

Now,Windows 7 Activation, I want to make sure that the contents of that region cannot be edited nor can they be deleted. To do this I can select the region I want to protect, then on the Developer tab and click the Group button circled in red below) to prevent the contents from being edited. You'll notice that you don't see any change in the document, but if I try to edit it, the status bar at the bottom tells you that "This modification is not allowed because this document is locked." Cool – it's locked. Since I want to also prevent it from being deleted, I click on the Properties button (in blue) and check the "Content control cannot be deleted" checkbox to also ensure it's not deleted.
The result: You can't edit or delete that legal text.
Here are the locations of the two commands I used:

Locking in Word 2007
That specific example shows you the power of the grouping functionality in Word, but there are several editing protection options available with content controls in Word:
For all content controls, if you look at their properties using the Properties button, we support two types of locking, which can be used together or individually:
Prevent the content control from being deleted Prevent the contents of the control from being edited
We chose to separate them like this because when we looked at how people wanted to lock down documents,Microsoft Office 2010, there were two distinct things they wanted to do:
For #1, it's about making sure that a particular content control is not accidentally deleted by the user. For example, I have a Date on a cover page. I want you to be able to type whatever date you want, but I need to make sure that the Date is never deleted –for compliance/archiving purposes,Office 2010 Activation, or because there's some process the document goes through which must know that date. In that case, I just want to prevent it from being deleted.
For #2, it's about making sure that if you have something in your document, it looks exactly as it was intended to, and no modifications have been made to its contents. For example, by default we include an introductory paragraph about my company on all client-facing proposals, talking about our history. Now, if the analyst in charge thinks that unnecessary, he can delete it; but if it is present, company policy dictates that it has to read as it exists today.
When I mix them both, I get the effect of the legal clause – that text can't be edited *or* deleted.
The locking options appear in the Locking section of the properties:

Now, in the example of the legal clause, I didn't use any of the seven content controls – instead I used the Group command. "Group" is actually just a simple extension we built onto the controls after our research into protecting a document, and works like this:
It has no restrictions on what can be in the grouped region (like rich text controls) Those contents are always locked to prevent the contents of the control from being edited You can, as we did, turn on/off additional locking to ensure the grouped region is not deleted You can put child editable controls in them (okay, you can do this with rich text too, but it's so important and cool that I wanted to explicitly mention it) The grouped region shows no indication in the UI that it's locked.
Now, the last point is the most significant. We haven't talked about the UI for content controls yet (another majorly cool area of enhancement for structured editing we've informally termed "the acetate layer" that we'll talk about in a future post), but we found there are lots of cases where you don't want to show the grouped region to avoid "clutter" on the page (since these regions are typically pretty big). Hence, groups give you all the control with no UI.
This locking stuff is probably the thing I find most exciting about structuring documents (okay, well , I find it all exciting – I'm a simple man) since it fills a need that we see all the time when we go out and talk to people/companies that use Word as part of their everyday process.
- Tristan
<div