I just finished a White Paper in which I showed what the load behavior of COM Add-ins, Normal.Dotm and Global Templates in Microsoft looks like Word 2010. I was prompted to write this paper in response to two things. First, I recently saw a presentation that was offered to a wide audience of legal technology leaders, staff, and trainers. The presentation erroneously stated that Microsoft Word’s load order was COM Add-in, Normal.dotm, and then Global Templates. Second, I received a panicked call from a client, who was told by a vendor that all their code should be in Normal.dotm. I was blown away by that. Its poor advice based on current best practices.

Here at Esquire Innovations, we follow the approach that the Normal.dotm should be left for the user, and that any firm customizations and additional add-ons to Word should be either COM Add-ins or Global Templates.

What is Load Behavior?

The load behavior of Microsoft Word 2010 (hasn’t changed since Word 97) refers to the way extended applications, or Add-ins, are loaded on startup. Add-ins contain automation that allow developers to build in features that are not part of the out-of-the-box installation of Word. These Add-ins can be in the form of COM Add-ins, adding to the existing Normal.dotm, or Global Templates.

In this White Paper, I explain:
• COM Add-ins
• Global Templates
• Normal.dotm
• Microsoft Word’s Load Behavior
• Why the Load Behavior is Important

Get the White Paper here.

I love non-linear prose (oxymoron?) – with a cohesive thread… so this will make sense.

How about a new marketing term called Reciprocal Marketing Exchange (RME).

[You heard it here first. I googled it…not there]

RME is the umbrella term that encompasses:

•  Reciprocal Link Exchange
  I put your web site’s link on our site and you put our link on yours.

• Client Case Studies
  The client invests in our product, we make them successful, and they let us write about it

•  Business –to-Business Promotion
  We tell our clients great things about your Business and you tell great things to your clients about ours.

• Business Partnership Network for Client discounts
  If a clients buys a product in the Business Partnership Network they get a discount.

• Editorial Exchange
  We pay for ad in your magazine or web-zine, you write a positive article about us or let us write a positive article about us.  AND you include a really good press release about us.

• Piggyback Trade Booth
  You and your marketing collateral can hang out in our trade booth, and we in yours.

• Tweet Exchange
  I tweet about you and you tweet about me.

• New one -Reciprocal Client Quote (googled it… not there)
  Give us a great quote and let us explain why it’s great.

• … This list can go on…

Now back to “To Say The Consultant Loved iCreate Would Be An Understatement” and the new RME – Reciprocal Client Quote.  The Reciprocal Client Quote is a great opportunity to explain from the business side why the quote is justified or can be substantiated from the business point of view.

Reciprocal Client Quotes

This consultant is implementing iCreate 7 at a client site.

Client: Each and every button on the iHyperstyles [vis-à-vis iCreate] ribbon addresses a real problem on the floor.  It is extremely intuitive and I can’t wait to teach it.
Randall Farrar: We thought hard and long when we were migrating iCreate 4 to Office 2007/2010. Let’s make the interface simpler and incorporate a REAL workflow intuitive user interface for the user.  Let’s take the positive feedback and negative feedback on the old iCreate, make it better, and at the same time leverage our Enhanced Native Architecture™ approach to development.

Client: I love the [iCreate] calendar.  No other [template] product I’ve used has it.
Randall Farrar (me): The iCreate Calendar is something I created for a previous product 15 years ago and incorporated it into iCreate 11 years ago.  Secretaries love it!  You can take Microsoft Outlook calendar information from one or several attorneys and incorporate it into one calendar in Microsoft Word.  Something Outlook can’t do or do well.  You can insert the iCreate Calendar in an existing document or create a calendar of events in a separate document.  Very cool.  For iCreate 7, my .NET developers made it much better by adding more flexibility and built it right into the iCreate 7 framework.  I’ve been humbled.

Client: I love the Clean Manual Numbering.  So easy. I loved SuperPaste. I love SuperCopy. I love all of iCreate’s clean-up features!
Randall Farrar: One major irritation for me is that we’ve been competing against competitors’ stand-alone clean-up tools that end up costing firms huge amounts of yearly dollars.  It turns out very few users in a firm use them. These products are complicated and designed for power Word users. We strategically decided to invest in “document clean up” and add those features right into iCreate 7.  What’s exciting is that we have only just begun to help users clean-up old documents (or new ones)  and help firm’s promote best practices with Microsoft Word.  We have some very cool features planned for the future.

Client: I love TitleMarks!
Randall Farrar: iCreate 7 leverages Word’s Paragraph Separator, by making it easy or automatic when separating Table of Content headings from the rest of the paragraph.

Client: At first I was skeptical about the  “New Outline Scheme” feature before I even used it. After I used them, I was thinking I was leaving something out, because it took 3 hours to do it in our previous solution, and I would always talk the user into just typing the numbers manually.
Randall Farrar: Yes iCreate 7’s Outline Scheme feature is a combination of outline numbering and styles on steroids.  Numbering is now easy for the user. No heavy lifting.

Client: Round-tripping was a huge problem with our previous solution, but not with iCreate
Randall Farrar: We know that users clone old documents, they create new ones… and more importantly, Microsoft Word work product can get very complicated structurally.  iCreate 7 allows the user to do all this and at the same time allow the user to collaborate with outside entities without any special automation on either end to make the documents work.  Word documents should just work.

Client: You’ve thought of everything. Wow, very smart!
Randall Farrar: Our mission statement is simple:
Innovative Software + Astonishing Services = Extraordinary Client Success

We had a bunch of complex documents (for a custom project) this week that had massive amounts of bookmarks (over a 1,000) and Styles that had to be removed along with some find and replace code.

Each time we ran the code against these documents we got the “Out-of-Memory” error in Microsoft Word. Microsoft’s solution (http://support.microsoft.com/kb/279675 – they are aware of this) is to save the file to clear up some memory. I’ve run into this before and saving does, SOMETIMES, helps.

But in this particular case YOU DON’T want to save the users changes… they may want to close the file without saving it and start over again.

Here’s how we fixed it:

Here is one of those features that is pretty much buried, but VERY useful.

In Office 2007 Word, Excel, and PowerPoint applications, clicking the Office button displayed a menu with items such as New, Open, Save, and Print in the left pane. Recent Documents were displayed in the right pane. In Office 2010, the Office button is gone. Instead, there is the File tab, clicking it opens up Backstage View – which has three panes.

By default, to see your Recent Documents, you have to go to Backstage View and click Recent in the left pane.

What if you want to see your Recent File list as it appeared in previous versions of Office (well almost)? You can!

At the bottom of the list of Recent Documents, you’ll see the “Quickly access this number of Recent Documents” check box, with a drop-down box to set the number. After enabling this option, your recent documents are now listed in the left pane of the Backstage View.

I’m finding myself adding more important hard to get to commands to the Quick Access Toolbar (QAT).  What happens if you reinstall Windows, you reinstall Microsoft Office, or you want to propagate that file to other users?  Thankfully, you can create a back-up of the QAT.

Use Explorer to navigate to:

• In Windows XP – C:\Documents and Settings\[username]\Local Settings\Application Data\ Microsoft\Office
• Windows Vista or Windows 7 – “C:\Users\[username]\ AppData\Local\Microsoft\ Office

In this location you will find QAT files called:

• Excel.qat – Microsoft Excel
• olkaddritem- Microsoft Outlook Contact
• olkapptitem – Microsoft Outlook Appointment
• olklogitem – Microsoft Outlook Journal
• olkmailitem.qat – Microsoft Outlook new email message
• olkmailread.qat – Microsoft Outlook read message
• olktaskitem – Microsoft Outlook new Task
• PowerPoint.qat – Microsoft PowerPoint
• Word.qat – Microsoft Word

Viewing Your QAT File

QAT files are XML files that you can view and edit in Notepad.  You can also copy and rename a QAT file to “.XML”, double click it and view it in Internet Explorer.

The Start of The Microsoft Office Synchronous XML Epoch

On January 30, 2007, the Microsoft Office Asynchronous Binary era, with its shrouded commands, cascading menus and copious toolbars, ended with Office 2003. With trepidation, those of us who had a personal eighteen-year business relationship with it knew what was coming. We had a choice; we needed to either acclimatize to this new environment or fall behind technically like those who clung to Lotus 1-2-3 and WordPerfect 5.1.

I can even remember BEGGING the Lotus rep for a Windows version of 1-2-3, and he said, “We’re sticking with DOS for now” WHAT A MISTAKE!

The Microsoft Office Synchronous XML version of Office (Microsoft Office 2007) ushered in an epoch of user interface paradigm shifts and new file formats. For those of us who find ourselves caught between these two eras and want to transverse from one to the other, it is important to understand why and how to make this crossover.

Eighteen years prior to January 30, 2007, firms invested hundreds of thousands of dollars over time on various versions of Microsoft Office. I call this the Microsoft Office 2003 era. It began in 1992 with Office 3.0 and ended with Office 2003. A huge investment was made in training, in-house development, product support, and additional Microsoft Office integration applications.

Microsoft Office Asynchronous Binary Age was built on the abstruse file formats of Microsoft Word, Excel, and PowerPoint. These file formats were created in the early 90’s when each of the Microsoft Office applications were relatively simple. As Microsoft added more features, the binary format became more complex with each Microsoft Office version. The documentation for the binary file format was very complex, which few understood which made working with the binary format outside the intrinsic Microsoft Office application very difficult. Very often, the internal binary format would become flawed and “file corruption” ensued or the document would behave strangely, rendering the document difficult to manage.

Additionally, this phrase “file corruption” (whether or not it was) was sometimes substituted as an excuse for poorly trained users and weak best practices. In this era, many important features were buried amongst numerous toolbars. Fantastic tools, macros, and applications were built to fix document problems. This allowed users to produce digital work product that was sub-par, but looked great when printed. Over time, users got used to the complex mix of user-interface-design elements and became accustomed to poorly formatted documents.

The version changes of Microsoft Office in this age consisted of slight cosmetic changes, menu changes, new menu items and the addition of even more features. For many firms there wasn’t a compelling reason to upgrade from one version to the next, and if they did migrate to a new Microsoft Office version, training on the new versions became less and less of an issue because the differences were insignificant. Most firms skipped versions, which helped reduce costs.

The Microsoft Office Synchronous XML Epoch

Epoch (ee-pok) means the “the beginning of a distinctive period in the history of anything.” This new Microsoft Office Synchronous XML era truly signifies the start of a new age with Microsoft Office. It is the first time in Microsoft Office’s history where firms have a choice in a migration starting point, if the firm has already purchased Microsoft Office 2007 and have not implemented it. In my opinion, there are no significant differences in Microsoft Office 2007 and 2010 for a firm traversing from the previous Microsoft Office era.

This is the case for a couple of reasons. First, Microsoft Office 2007 hit the market during a worldwide economic crisis and most firms just couldn’t afford, or were apprehensive about, the costs of training and infrastructure upgrades. Migrating to Microsoft Office 2007 was that reality. Second, the climacteric change was so drastic that firms paused to take a longer look at it. It was an unfortunate time for Microsoft Office solution providers, firms, and Microsoft. The firms that did migrate to Microsoft Office 2007 are presently ahead of the technical evolutionary power curve.

Synchronous in the New Era

What do I mean by the synchronous nature of the new Microsoft Office? I mean that commands and features are contextual to what the user is doing. For example, if a user is working in a Word table the commands associated with the features for tables are dynamically available to the user, via a Ribbon. In the old Microsoft Office era, the table features were buried in a menu and a toolbar. The user now doesn’t have to know where those features are or search for them; they are just “there.”

By replacing toolbars with Ribbons, the user is presented with a contextual interface that provides functionality based on the context the user is working in. The Ribbon user interface provides the user with graphical representations of document control features grouped by functionality. The Ribbon may also contain Tabs to expose different sets of features eliminating the need for different icon based tool bars.

This synchronous nature is propagated throughout all the Microsoft Office applications. By being more intuitive, the long-term costs of ownership are truly lower with this new Microsoft Office epoch.

XML in The New Era

From a technical point of view, the differences in Microsoft Office’s new file format are on a magnitude that it cannot be called an improvement in a species, but rather the creation of a new genus. The new file format is XML (Extensible Markup Language). This new file format can be accessed without using the intrinsic Microsoft Office application, such as Word. Microsoft Word (or Excel and PowerPoint) is no longer needed to create or edit a document. This ease of file access means that document content and metadata can easily be viewed and changed. The new XML file format is smaller, thus making it a more efficient digital format for web or cloud based applications.

To be successful in any new environment you have to embrace it in order to thrive and grow. This holds true for the new Microsoft Office XML file format. Even though the new Microsoft Office versions (2007 and 2010) allow files to be saved in the old binary format, in my opinion, the new format should be unconditionally embraced. To hold-on to the old binary format is only placing your firm in precarious position of future collaboration issues with your clients and cloud based applications.

The Microsoft Office Synchronous XML Epoch Has Started

The Microsoft Office Asynchronous Binary Age is over, and for good reason.

It was a dead-end productivity environment. It was bound to die a slow death like many other technologies of the past. The Microsoft Office Synchronous XML Epoch brings together modern technologies such as XML and a synchronous user interface experience that increases productivity and reduces long-term cost of ownership. Depending on your current version of Microsoft Office, the result is that you should be traversing to either Microsoft Office 2007 or 2010, sooner rather than later.

Wouldn’t it be nice to view your document and see the styles applied to each paragraph in the left margin? Well you can, by changing the “Style Area Width.”

1. Change the document view to Draft

a.  From the View Ribbon, click Draft.

2. Display the Style Width Area
   

   a.  Click the Office Button (in the top left hand corner of your window) and click the Word Options button.

   b.  Navigate to the Advanced menu and scroll down to the Display section.

   c.  In the “Style area pane width in Draft and Outline views” type the width you want to display in the margin, such as 0.75.”

   d.  Click the OK button.

The names of applied styles appear along the left margin for each paragraph.

Belaboring the antecedent to the use of Styles, i.e. Direct formatting, I want to remind those who still believe styles are a pain, that firms can transform their work product and morale when users implement styles in their Word documents. Yes… in a way, and implemented right… using styles can change lives… yea…ok, a little over the top.

Here’s my argument for using Microsoft Word Styles – The work product for law firms is documents. Thousands of documents are created on a daily basis. I believe the attorney’s role should be "word-smithing" for those documents, not formatting text and paragraphs.  What a waste of time!  So much time can be spent getting formatting "to just work" in Microsoft Word, that word-smithing is shortchanged…resulting in decreased currency. Using Styles will provide your firm with distinct advantages.

• Faster Formatting: All the bold, underlines, font sizes, paragraph indents, etc, can be contained in just one style.
• Consistent look and feel to firm documents: When the same styles are used across the board in a firm, the documents have a consistent look and everyone knows how to work with them.
• Global Formatting: If you have a 60-page agreement and you need to change the font size on fifty headings in the document, you had better know how to do some advanced find and replace or you’ll have to go to each heading and change it manually. With Microsoft Word Styles, you can change the style once and it is automatically changed throughout the document.
• Building Tables of Content: Using Heading styles makes creating TOCs automatic.
• Documents are smaller: The amount of space a style definition takes up in a document is significantly less than all the direct formatting applied to fonts and paragraphs.
• Stable Documents: Documents that are correctly formatted using styles are less likely to become problem documents later in the document lifecycle, saving time and frustration down the road.

Here’s a function that will tell you if the word document needs to be saved:

Read Randy’s latest article on metadata.

First published by the New York City Chapter of the  ALA .

Written by me and originally printed in the March 2010 issue of the Minnesota ALA’s Verdict Newsletter

On January 26, 2010, Minnesota’s Lawyers Professional Responsibility Board released Proposed Opinion No. 22 that deals with a lawyer’s ethical obligations regarding metadata, as follows:

“A lawyer has a duty under Rule 1.6, Minnesota Rules of Professional Conduct (MRPC), not to knowingly reveal information relating to the representation of a client, except as otherwise provided by the Rules. The lawyer’s duty not to knowingly reveal such information extends to and includes metadata in electronic documents. Accordingly, a lawyer is ethically required to take reasonable care to avoid improper disclosure of confidential information in metadata in electronic documents. If a lawyer receives a document which the lawyer knows or reasonably should know contains inadvertently sent metadata, the lawyer shall promptly notify the document’s sender as required by Rule 4.4, MRPC.”

For the full draft of the opinion including the applicable rule and other published opinions on metadata, visit http://www.mncourts.gov/lprb/Opinion22.pdf

Get the full article here

It all boiled down to how custom XML was accessed. For those vendors who decided to go with XML Tags it didn’t go well. They had either to drop out of the Template market or rewrite their code.

We decided, early on, to use content controls in iCreate v7. On the down side, Content controls were not backward compatible with Office 2003, but we felt that Microsoft’s content controls were the future. Content controls are flexible, dynamic and can be built to be very smart. PLUS, I couldn’t stand the way XML Tags looked in the document. If not done right they could throw off pagination. That would’ve been a support nightmare.

Join us for a free iCreate webinar tomorrow (3/17/2010) that shows the power of Office 2007

iCreate: Smart document templates and formatting for law firms – https://www1.gotomeeting.com/register/681602433

Below is a matrix that shows how iRedline enhances the Microsoft Word 2007 comparison and collaboration process. I hope to make you a believer in the Word 2007- iRedline 7 combination.

I often am asked, “How does iRedline handle tables during the comparison process?” I say, “Great, because iRedline leverages Word 2007’s comparison engine, and Word tracks revisions in tables accurately.” This question is asked because comparison products that compare tables (Word documents) outside of Microsoft Word use very different comparison algorithms and usually have a difficult time with Words tables, especially complex tables, and the resulting documents have messed up table.

Under the hood, Word tables are very complex, and in Word 2007, they have hit a completely new level. I believe this is one of the reason many OpenXML (Microsoft Office’s new file format) will make it difficult for many non-Microsoft document viewers to show Word’s tables with Tracked Changes accurately. I’m amazed at how well Word handles tables during the comparison and document revision (Track Changes turned on) process, because of this complexity.

Observe the simple table below. This table has two deletions, one insertion and three deleted cells (pink). Yet look at the underlying OpenXML code below (see Simple Table as OpenXML Code) is very complex. The OpenXML code lists 18 revision changes and many of them are nested inside other changes.

 

Simple Table as OpenXML Code

<w:tbl xmlns:w="http://schemas.openxmlformats.org/
wordprocessingml/2006/main">

  <w:tblPr>

    <w:tblW w:w="0" w:type="auto" />

    <w:tblBorders>

      <w:top w:val="single" w:sz="12" w:space="0" w:color="auto" />

      <w:left w:val="single" w:sz="12" w:space="0" w:color="auto" />

      <w:bottom w:val="single" w:sz="12" w:space="0" w:color="auto" />

      <w:right w:val="single" w:sz="12" w:space="0" w:color="auto" />

    </w:tblBorders>

    <w:tblLayout w:type="fixed" />

    <w:tblCellMar>

      <w:left w:w="30" w:type="dxa" />

      <w:right w:w="30" w:type="dxa" />

    </w:tblCellMar>

    <w:tblLook w:val="0000" />

    <w:tblPrChange w:id="0" w:author="Randall Farrar">

      <w:tblPr>

        <w:tblW w:w="0" w:type="auto" />

        <w:tblBorders>

          <w:top w:val="single" w:sz="12" w:space="0" w:color="auto" />

          <w:left w:val="single" w:sz="12" w:space="0" w:color="auto" />

          <w:bottom w:val="single" w:sz="12" w:space="0" w:color="auto" />

          <w:right w:val="single" w:sz="12" w:space="0" w:color="auto" />

        </w:tblBorders>

        <w:tblLayout w:type="fixed" />

        <w:tblCellMar>

          <w:left w:w="30" w:type="dxa" />

          <w:right w:w="30" w:type="dxa" />

        </w:tblCellMar>

        <w:tblLook w:val="0000" />

      </w:tblPr>

    </w:tblPrChange>

  </w:tblPr>

  <w:tblGrid>

    <w:gridCol w:w="3240" />

    <w:gridCol w:w="180" />

    <w:gridCol w:w="840" />

    <w:gridCol w:w="1440" />

    <w:tblGridChange w:id="1">

      <w:tblGrid>

        <w:gridCol w:w="3240" />

        <w:gridCol w:w="90" />

        <w:gridCol w:w="90" />

        <w:gridCol w:w="1440" />

      </w:tblGrid>

    </w:tblGridChange>

  </w:tblGrid>

  <w:tr>

    <w:trPr>

      <w:trHeight w:val="310" />

      <w:trPrChange w:id="2" w:author="Randall Farrar">

        <w:trPr>

          <w:trHeight w:val="310" />

        </w:trPr>

      </w:trPrChange>

    </w:trPr>

    <w:tc>

      <w:tcPr>

        <w:tcW w:w="3240" w:type="dxa" />

        <w:shd w:val="clear" w:color="000000" w:fill="auto" />

        <w:tcPrChange w:id="3" w:author="Randall Farrar">

          <w:tcPr>

            <w:tcW w:w="3240" w:type="dxa" />

            <w:shd w:val="clear" w:color="000000" w:fill="auto" />

          </w:tcPr>

        </w:tcPrChange>

      </w:tcPr>

      <w:p>

        <w:pPr>

          <w:pStyle w:val="Heading1" />

          <w:numPr>

            <w:ilvl w:val="0" />

            <w:numId w:val="0" />

          </w:numPr>

          <w:rPr>

            <w:b />

            <w:i />

            <w:color w:val="000000" />

          </w:rPr>

        </w:pPr>

        <w:r>

          <w:rPr>

            <w:b />

            <w:color w:val="000000" />

          </w:rPr>

          <w:t>Chemical Composition</w:t>

        </w:r>

      </w:p>

    </w:tc>

    <w:tc>

      <w:tcPr>

        <w:tcW w:w="180" w:type="dxa" />

        <w:shd w:val="clear" w:color="000000" w:fill="auto" />

        <w:tcPrChange w:id="4" w:author="Randall Farrar">

          <w:tcPr>

            <w:tcW w:w="180" w:type="dxa" />

            <w:shd w:val="clear" w:color="000000" w:fill="auto" />

          </w:tcPr>

        </w:tcPrChange>

      </w:tcPr>

      <w:p>

        <w:pPr>

          <w:rPr>

            <w:b />

            <w:color w:val="000000" />

          </w:rPr>

        </w:pPr>

      </w:p>

    </w:tc>

    <w:tc>

      <w:tcPr>

        <w:tcW w:w="840" w:type="dxa" />

        <w:shd w:val="clear" w:color="000000" w:fill="auto" />

        <w:cellDel w:id="5" w:author="Randall Farrar" />

        <w:tcPrChange w:id="6" w:author="Randall Farrar">

          <w:tcPr>

            <w:tcW w:w="840" w:type="dxa" />

            <w:shd w:val="clear" w:color="000000" w:fill="auto" />

            <w:cellDel w:id="7" w:author="Randall Farrar" />

          </w:tcPr>

        </w:tcPrChange>

      </w:tcPr>

      <w:p>

        <w:pPr>

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

        </w:pPr>

      </w:p>

    </w:tc>

    <w:tc>

      <w:tcPr>

        <w:tcW w:w="1440" w:type="dxa" />

        <w:shd w:val="clear" w:color="000000" w:fill="auto" />

        <w:tcPrChange w:id="8" w:author="Randall Farrar">

          <w:tcPr>

            <w:tcW w:w="2400" w:type="dxa" />

            <w:shd w:val="clear" w:color="000000" w:fill="auto" />

          </w:tcPr>

        </w:tcPrChange>

      </w:tcPr>

      <w:p>

        <w:pPr>

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

        </w:pPr>

        <w:del w:id="9" w:author="Randall Farrar">

          <w:r>

            <w:rPr>

              <w:color w:val="000000" />

            </w:rPr>

            <w:delText>Typical</w:delText>

          </w:r>

        </w:del>

      </w:p>

    </w:tc>

  </w:tr>

  <w:tr>

    <w:trPr>

      <w:trHeight w:val="310" />

      <w:trPrChange w:id="10" w:author="Randall Farrar">

        <w:trPr>

          <w:trHeight w:val="310" />

        </w:trPr>

      </w:trPrChange>

    </w:trPr>

    <w:tc>

      <w:tcPr>

        <w:tcW w:w="3240" w:type="dxa" />

        <w:shd w:val="clear" w:color="000000" w:fill="auto" />

        <w:tcPrChange w:id="11" w:author="Randall Farrar">

          <w:tcPr>

            <w:tcW w:w="3240" w:type="dxa" />

            <w:shd w:val="clear" w:color="000000" w:fill="auto" />

          </w:tcPr>

        </w:tcPrChange>

      </w:tcPr>

      <w:p>

        <w:pPr>

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

        </w:pPr>

        <w:r>

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

          <w:t>Ca(OH)</w:t>

        </w:r>

        <w:r>

          <w:rPr>

            <w:color w:val="000000" />

            <w:vertAlign w:val="subscript" />

          </w:rPr>

          <w:t>2</w:t>

        </w:r>

        <w:r>

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

          <w:t xml:space="preserve"> </w:t>

        </w:r>

      </w:p>

    </w:tc>

    <w:tc>

      <w:tcPr>

        <w:tcW w:w="180" w:type="dxa" />

        <w:shd w:val="clear" w:color="000000" w:fill="auto" />

        <w:tcPrChange w:id="12" w:author="Randall Farrar">

          <w:tcPr>

            <w:tcW w:w="180" w:type="dxa" />

            <w:shd w:val="clear" w:color="000000" w:fill="auto" />

          </w:tcPr>

        </w:tcPrChange>

      </w:tcPr>

      <w:p>

        <w:pPr>

          <w:jc w:val="center" />

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

        </w:pPr>

      </w:p>

    </w:tc>

    <w:tc>

      <w:tcPr>

        <w:tcW w:w="840" w:type="dxa" />

        <w:shd w:val="clear" w:color="000000" w:fill="auto" />

        <w:cellDel w:id="13" w:author="Randall Farrar" />

        <w:tcPrChange w:id="14" w:author="Randall Farrar">

          <w:tcPr>

            <w:tcW w:w="840" w:type="dxa" />

            <w:shd w:val="clear" w:color="000000" w:fill="auto" />

            <w:cellDel w:id="15" w:author="Randall Farrar" />

          </w:tcPr>

        </w:tcPrChange>

      </w:tcPr>

      <w:p>

        <w:pPr>

          <w:jc w:val="center" />

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

        </w:pPr>

      </w:p>

    </w:tc>

    <w:tc>

      <w:tcPr>

        <w:tcW w:w="1440" w:type="dxa" />

        <w:shd w:val="clear" w:color="000000" w:fill="auto" />

        <w:tcPrChange w:id="16" w:author="Randall Farrar">

          <w:tcPr>

            <w:tcW w:w="2400" w:type="dxa" />

            <w:shd w:val="clear" w:color="000000" w:fill="auto" />

          </w:tcPr>

        </w:tcPrChange>

      </w:tcPr>

      <w:p>

        <w:pPr>

          <w:jc w:val="center" />

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

        </w:pPr>

        <w:r>

          <w:rPr>

            <w:color w:val="000000" />

          </w:rPr>

          <w:t>96.</w:t>

        </w:r>

        <w:del w:id="17" w:author="Randall Farrar">

          <w:r>

            <w:rPr>

              <w:color w:val="000000" />

            </w:rPr>

            <w:delText>0%</w:delText>

          </w:r>

        </w:del>

        <w:ins w:id="18" w:author="Randall Farrar">

          <w:r>

            <w:rPr>

              <w:color w:val="000000" />

            </w:rPr>

            <w:t>5%</w:t>

          </w:r>

        </w:ins>

      </w:p>

    </w:tc>

  </w:tr>

</w:tbl>

<w:p xmlns:w="http://schemas.openxmlformats.org/
wordprocessingml/2006/main" />

 

Navigating through your document using Words Next and Previous revision buttons is straight forward, except when there are comments in your document. This is when you’ll get a little surprise. With comments in your document, and while you’re navigating through your document, Word will automatically open up the Reviewing Pane (if it’s not already open) when it hits a comment. Word then places the insertion point in that comment in the Reviewing Pane. At this point, you’re no longer in the document; rather you’re in the Reviewing pane.

Don’t panic, because if you click the Next or Previous button again it goes on to the next or previous revision in the document and out of the Reviewing Pane. Things only get sticky when you actually click in the Review Pane (it’s now the active Window) and at this point you’ll be navigating inside the Reviewing Pane (see How to Navigate your Revisions Inside the Reviewing Pane). You have to click back into your document or close the Reviewing Pane.

Solutions:

• Close the Reviewing Pane when it appears using the keyboard shortcut Shift+Alt+C.
• Hide your comments in the Show Markup option by unchecking comments in the drop-down list (see Figure – Show Markup below).

Show Markup

 

iRedline handles this much more elegantly by ignoring the comments (using iRedline’s Next and Previous buttons) and navigating only the revisions in your document.

 

 

Most people don’t know that you can use the inside of the Reviewing Pane (see Figure – Reviewing Pane below) to navigate your revisions. When you use the Reviewing Pane in this way, you’ll actually be navigating from one revision to the other inside the Reviewing Pane. This approach will highlight each revision inside the Reviewing Pane and at the same time scroll the document to show where that revision is located.

How to Navigate your Revisions inside the Reviewing Pane

1. Point to a revision text beneath the bordered change type in the Reviewing Pane with your mouse pointer
2. Click your mouse
3. Click the Next button to navigate to the next revision
   The next revision will be highlighted and you’ll see the actual revision in your document to the right.

The Reviewing Pane

 

 

When working with rows and cells in a table, word will only be able to track inserted and deleted cells, while editing. Word is unable to track merged or split cells. Merged and split cells can only be tracked when you compare or combine documents… in Native Word or iRedline v7.

Unfortunately there are no keyboard shortcuts for the Previous and Next button for navigating your revisions. Word forces you to use your mouse.

A way to solve this is to map two keyboard shortcuts to the Word commands:
NextChangeOrComment and PreviousChangeOrComment.

iRedline v7 has solved this by mapping the keyboard shortcuts to iRedline’s Previous and Next revisions navigation button (which also gives you’re the ability to navigate DeltaView changes):

Move to Previous revision – Ctrl+Alt+P
Move to Next revision- Crtl+Alt+N

Often it isn’t obvious where a move tracked change has moved to or moved from, because it may be on another page. I really like the way Microsoft has implemented this feature. Using your mouse, right-click on a move and select Follow Move in the short cut menu (click image below). This simple short-cut will navigate to the related move.

Navigating Moves

From the TheNextWeb blog:

“…Google just announced in an email to Google App admins that starting “in a few weeks” Google Docs published and shared to users outside of one’s domain and linked to from a public website will be crawled, indexed and appear in Google search results. “This is a very exciting change as your published docs linked to from public websites will reach a much wider audience of people,” said Google in its announcement…”

Excited?! No… they said “very excited.” Yea, we want our documents read by a “much wider audience.” Not! And I thought document metadata was high risk.

The blog goes on to say…

“Thankfully, Google has given Google App admins the ability to regulate sharing to users outside of their domain. However, the sharing options that Google currently offers are not nearly as granular as they need to be. Businesses using Google Apps may likely want tiers of users giving some the ability to share while prohibiting others. In addition, a business might also want to allow sharing with users of specific domains while prohibiting all others…”

This will kill Google Docs or relegate it to a niche market. What law firm or company wants a document accidentally indexed and shown to the world? It only has to happen once. A miss step on Google’s part. Trust me, enterprises are not going to trust their users to not “publicly publish”.

Man… right when I was going to put resources into this platform! Forget that…for now. Then, if Google uses attenuated terms like “document management” or “knowledge management” they may get some traction.

Can someone recommend an organic spider insecticide?

Read full blog here…