[Originally appeared 2000.]

We continue the series on collaboration, written by Bob Blacksberg in collaboration with Sherry Kappel of Microsystems. We have been reviewing third party tools for document comparison, looking to find solutions to the difficulties encountered with Word’s internal Track Changes and Compare Documents functions. In Word of Law No. 35 we quoted the Microsoft Legal Users Guide’s recommendation to law firms that a third party tool should be used for document comparison. A reader directed us also to guidance not to use both Word’s internal Track Changes feature and CompareRite.

In this week’s column, we consider the document comparison capabilities of Adobe’s Acrobat and Workshare’s DeltaView.

Similar to Lexis-Nexis CompareRite, the Compare Pages function of Adobe’s Acrobat delivers a report of changes between one document and another. Thus it supports the Comparison function, but not Tracking or Incorporation, that we have described in the preceding Word of Law columns. Acrobat’s technology avoids the document formatting and appearance issues that we have covered in the preceding columns, since the PDF (Portable Document Format) files are created from the print process.

There are several drawbacks to document comparison with Adobe Acrobat. These limit its effectiveness and practicality as a solution for document comparison and collaboration in legal practice and other work that requires a high degree of document comparison precision.

The Compare Pages function of Acrobat only highlights broad portions of text as changed, either entire pages, or significant portions of pages. Thus it does not offer the capability of showing changes in specific wording or sentences, or indicate text has been moved. It does not explicitly mark insertions and deletions.

The process of producing such a PDF comparison report from Word requires publishing both the original and the revised Word documents to PDF, then comparing the pages to determine the changed results. This function requires the full licensed version of Adobe Acrobat, not just the free and widely used Acrobat reader.

While these shortcomings make Acrobat fall short as a tool for supporting the document comparison functions we have sought, it can play a significant role in document collaboration under some circumstances. Publishing to Acrobat solves format incompatibilities among collaborators. If responsibility for editing is not shared among collaborators, then the PDF format and Acrobat’s tools include many features that assist in collaboration, such as document annotations. Publishing to PDF avoids transmitting undesirable information about the drafting process to third parties.

The newest document comparison product, DeltaView from Workshare Technology, Inc. (www.workshare.net) raises the bar significantly in its capabilities and performance in document comparison. It deserves serious evaluation by legal practices and any organization that requires intensive comparison of Microsoft Word documents. The availability of the most recent version, 2.5, was announced on August 17, 2000. The descriptions here are based on that version.

Where CompareRite was designed as a tool to create paper images of the results of document comparison and Adobe Acrobat was designed to create the electronic analogue in its print and page oriented presentation, DeltaView has been designed to create an on screen environment rich in its capabilities of supporting the document comparison, review and incorporation process. It also thoroughly supports printed reports of comparisons.

DeltaView works by launching a session with Word, opening the original and revised documents, then, using the inherent RTF SaveAs filters of Word, DeltaView creates a rich formatting context in which comparison of the document content can begin. Again, like Acrobat and CompareRite, DeltaView delivers a report of the changes. This report is delivered in either a .WDF (a Workshare proprietary format) readable by DeltaView, or an RTF file format which would then enable an editable report by any application which can read or open an RTF file format, or as a Microsoft Word document.

DeltaView’s onscreen review environment offers a multi-paned view of the document comparison report. It can show the results of comparison only, or present simultaneous views of the comparison results, together with either or both of the original document and the modified document. It can also present a pane with a summary of document changes. Navigation tools include backward and forward arrows to move from change to change, as well as live links between the document change summary and the changes in the document. All of the visible windows are linked, so navigating in any of the views moves the other open windows with this.

This multiple view addresses the concerns about legibility of document comparison that we described in issue 29. While the comparison report indicates where changes occur, comprehension of the meaning of the revised text often requires a “clear” reading of the modified document.

DeltaView supports comparison to show changes in formats, and, in a development most welcome, shows a variety of change in tables, including addition and removal of table cells. The rendering set allows distinctive coloring of inserted, deleted and moved table cells. On screen, these indications are very clear. For those relying on the printed output, the need to support color printing just grew.

The current version of DeltaView does not directly support Incorporation. An enhanced version of DeltaView, which Workshare calls “DeltaView Premier” is described on the Workshare web site, with an availability later this year. It will add an Incorporation function, making the “Modified” document window a functioning instance of Word linked to the other document comparison windows of DeltaView.

When the DeltaView comparison is saved to Word format, the markings for inserted, deleted and moved text use distinctive DeltaView styles. It would be possible to construct a macro based system for Incorporation, working with those styles. Given the support for that function in the Premier Version, such an effort needs to be weighed against waiting for Workshare to support this function.

Workshare’s experience with enterprise document tools shows in the features of DeltaView. The developers of DeltaView had been the authors of SafetyGain, a companion product that supports offline use of the document management system, DOCS Open. DeltaView includes enterprise configuration support, such as the management of rendering sets and integration with iManage, DOCS Open and WORLDOX document management systems. The additional collaborative capabilities of DeltaView Premier look intriguing. We will track those developments and report on them as that version of the product becomes available.

All of this discussion of document comparison requires some reminders of the importance of version control. That can lead off next week’s column.

This 2000 article originally appeared in Office Watch. Subscribe to Office Watch free at http://www.office-watch.com/.

[Originally appeared 2000.]

The Word of Law Column in the last issue began to answer the questions about collaboration begun in Word of Law No. 29. In answering, “What activities must be supported when drafting documents collaboratively,” we covered the first four of a list that included, “share, compare, track, review, comment, find, model, and reuse.” This week’s column picks up from there.

COMMENT

Drafting or review of documents may be accompanied by a simple or complex conversation among collaborators. They may cite references, share their analysis, explain their changes, even criticize or disagree with the author. Microsoft Word supports these kinds of functions in its comments function, but as convenient as that format may seem, we may not want to put comments in the body of documents where they could be preserved accidentally for unauthorized view. Comments may be found in transmittal letters, cover memos or e-mail transmittals. Their disconnection from the text may limit their value in the drafting process. The newest electronic or even web-based collaboration systems support discussion threads that may be associated with document drafts.

FIND

There can be no collaboration over a document, nor can any of its inherent activities be facilitated, if the document over which collaboration is required can’t be found! Thus, to support fully document collaboration in a cooperative setting, the collaborators must share methods of access and nomenclature, be able to view the history of the document, the ownership of the document, and, most importantly, the availability of the document. Sometimes this activity requires standardization of document locale. A document can be shared effectively when stored on a Web server and access is protected, perhaps on a document management system. The altogether too common attempts to administer and maintain collaboration of documents attached to e-mail messages are likely to cause difficulties.

MODEL

In many organizations, standards should play a significant role in our document drafting. The standards include both document formatting and content. Collaboration, especially in a cooperative environment, benefits significantly from preparing and using document standards. In this column, we have emphasized repeatedly the value of a common set of document styles, stored and applied through a set of Microsoft Word templates. The identification of standard text, or text components, enables collaboration to focus on the special elements, those for which our drafting effort has the highest value.

REUSE

This function is one which can simultaneously leverage the productivity of document collaboration, and which, if performed without skill, forethought, and best practices, can unravel and defeat the productivity we seek to gain. The reuse of document content has been a prevalent practice in our industry since the advent of computer-generated paper documents, yet some of these same unsuspecting practices exercised on an electronically collaborated document may actually harm our ability to reuse existing electronic content at all. Do we have readily available content to support our current drafting requirement? If so, is it accessible from a currently supported file format or does it require conversion? If the content does not require conversion, does the formatting associated to it require touch-up, or realignment to our current model? Do we have proper tools for conversion? Are we employing proper approaches for copying, cutting and pasting content between documents? Are we skillfully inputting our content such that it can be reused in a manner that survives beyond this document’s moment? Do we make proper document construction choices: when should we use a table vs. tabs?Are we using styles to impose our general format choices, and then using manually-applied formats only for occasional format situations? Each of these speaks to the reusability of our content – and to the productivity we can gain or lose by collaboration.

How should these activities be different when the collaboration context is cooperative, and when it is reviewed by the opposing side?

While we may wish to strengthen the collaborative environment in a cooperative context, we need to be careful about the information that we expose about the drafting of documents when the document is shared with or published to others who are do not work with us. When the opposing side only received paper copy, this barrier was easy to maintain. As we pursue the practice and tools of electronic collaboration, the easiest guideline should be that those outside our organization see only the finished draft or document that we intend for them to see, and do not have access to the other information, drafts or comments that we include in our systems for collaboration. Please note that those “inside” our organization for document drafting may include persons employed by others such as attorney and client.

This 2000 article originally appeared in Office Watch.Subscribe to Office Watch free at http://www.office-watch.com/.

[Originally appeared 2000.]

The Word of Law column published in Word of Law No. 29 began a series on collaboration. As we begin answering the questions posed in that column, the discussion may seem a bit abstract. Why take two or three columns before describing any specific information about Microsoft Word or other products? The answer lies in the role of system architect described issue 4.48. To make sense of the techniques and the need for tools inside and outside of Microsoft Word, we must have a common understanding of the activities to be supported when drafting collaboratively. Some of these points may seem basic. It doesn’t hurt to remember the basics when trying to accomplish something new or sophisticated. Also, as we look at the behavior of the collaborative tools and techniques, we need to define what we could and should do with them, before we can answer whether they work properly, or what works best.

What activities must be supported when drafting documents collaboratively?

We can distill collaboration to a series of verbs: share, compare, track, review, comment, find, model, reuse. Some of these activities are simple, others subtle. Some require a disciplined community of use in order to function effectively.

SHARE

Nothing could be more basic to collaboration than the notion that more than one person takes responsibility for writing and editing a document. The collaborators may be peers, as Sherry and Bob seek to be in preparing this series. They may consist of a chain of responsibility, such as author, proofreader and editor, or, in the context of law practice, paralegal, associate and partner. Shared responsibility for drafting may also be adversarial. At times, it may appear that lawyers have substituted the printed page for the field of battle. Note that in this description, we leave out author and secretary. This discussion concentrates on shared responsibility for the substance of documents. For this purpose, we will assume that the secretarial role does not include responsibility for the substance of a document, although in real life, the opposite is so often true.

Those who share responsibility for drafting a document must explicitly or implicitly agree on the methods and responsibilities. This used to be much easier. The author (with appropriate secretarial or printing assistance) typed and copied the draft or galleys and distributed them physically to the collaborators. The collaborators made changes by hand markup, or a combination of markup and correspondence suggesting revisions. The author accumulated the suggested or directed changes to produce a revised draft. Today’s electronic document sharing imposes new issues in the sharing process.

Although the concept of sharing is not limited to this meaning, it can be helpful in contrasting “review” activities by thinking about collaboration prior to publication or distribution of a draft document to “third” parties. Prior to distribution, the comments must be assembled into a single complete draft. At this point, the decisions about the methods and extent of markup and other document drafting information must be determined.

COMPARE

For many users, we could complete the story of collaboration at “share and compare.” In a drafting process that requires a series of revisions, the author must display to the rest of the collaborators the changes made between drafts. Text may have been inserted, deleted or moved. Sometimes formatting changes need to be highlighted, particularly if they indicate a change in the structure of a document. Document comparison may also be used forensically. A reviewer or adversary may receive a series of drafts of a document that have not been marked by the author, and wish to determine whether and what changes have been made.

In prehistoric times (sorry, we meant before widespread use of personal computers and contemporary word processing), document comparison required that drafts be marked by hand to show changes. Typically, inserted text was underlined and the locations of deleted text were marked with a carat (^) or other distinctive symbol. The use of red pen for the original markup led to the term “redline” for a document marked in this way, although the lack of color copiers led many of us to call these “blacklined” instead.

Word processing and especially the third party comparison programs have brought us computer generated markup to facilitate document comparison. We will examine these functions thoroughly in this series. For now, let’s focus on what document comparison should accomplish, both from the perspective of the collaborators and the computer. The collaborators need the markup to indicate to each other whether a change has been made in the text and the substance of the change. The markup need to be complete, neither missing the occurrence of changes nor marking unchanged text falsely as changed.

An aspect of this comparison process that receives little discussion might best be called “legibility.” The collaborators must be able to read both current and prior versions of a document clearly, able to follow its substance before and after the changes. The blacklined copy itself can easily lose legibility. If a paragraph includes several insertions and deletions, marked, for instance, in a series of brackets, double underlines and strikeouts, the effort to read either the current version straight through, or the prior version, can take significant mental effort. In Bob’s legal practice, when collaborating with others on the drafting of complex documents, he often distributed both changed pages, marked by manual or machine blacklining, and a clean revised copy of the document. The collaborators or reviewers were assumed to have the prior clean copy of the document. If the drafting were critical enough, the reviewer might work with all three of the blackline, the prior copy and the current copy arrayed on their desk. Microsoft Word offers some of this capability in the options available in its Track Changes feature. We will share concerns about the use of that feature, however, later in this series. DeltaView, the newest of the third party document comparison tools, supports a three pane view of the original document and revised document in their unmarked form, linked on the screen to the blacklined copy.

The issue of legibility helps demonstrate that there is no “perfect” document comparison. The “perfect” text lies in the old and new versions. The comparison, manual or machine, is only a tool for locating and indicating the changes.

TRACK

Word processing, aided and abetted by e-mail and other connectivity, have promoted an expansion and intensification of collaboration, whether in paper distribution and review of drafts or directly in electronic formats As the number of parties involved in a document’s collaboration grows and the expectations for turnaround time of drafts shrink, it has become necessary to manage the tasks and status of collaboration from a work flow perspective. Fully tracking these activities may involve designating a person as an overall sponsor of the document and performing the recordkeeping tasks associated to the parties involved in the documents’ creation, revision and distribution cycles. This function informs, monitors, and generates status surrounding the collective pursuit. Tracking, then, involves all activities associated to managing the document from its project perspective: who has responsibility for what section of the document, what timeframes must be met and what distribution mechanisms must be accommodated.

Conscious decisions need to be made about the level of detail that should be maintained of the document drafting process. The Track Changes feature of Microsoft Word records within the document the time and date on which each change was made and the name Word assigns to the “user” when the editing was made. This may or may not be desirable information to maintain within the document, especially when the electronic form of the document is distributed to adverse persons. It may be desirable to maintain an “audit history” of the document, recording who made what changes at what times.

A key issue in document drafting is when to save a file as a new version. Version control is key to performing document comparisons accurately and to maintaining the integrity of the audit history. At the very least, new versions are required for documents each time they are published and distributed.

REVIEW

It can be valuable to distinguish the review of a distributed or published draft from cooperative editing. A person defined as a reviewer generally will not have responsibility for making or affirming the changes to the proposed draft, especially if there are multiple reviewers. That responsibility will be kept with the document’s author or sponsor. It may be desirable to deliver a document to a reviewer in a form that does not permit them to edit the text, but only to annotate it. While distribution of paper copy without electronic versions suffices, in the electronic world, a similar approach can be accomplished by publishing documents to a non-editable form, such as Adobe Acrobat.

This may not be the best point to pause this discussion, but it has taken up the week’s worth of column space. We will pick up the trail with the Comment activity in the next issue.

This 2000 article originally appeared in Office Watch.Subscribe to Office Watch free at http://www.office-watch.com/.

[Originally appeared 2000.]

Shared responsibility for the drafting and editing of documents can hardly be said to be unique to the practice of law. Yet lawyers do so with an intensity and attention to detail (perhaps better termed an obsession) difficult to match in any other document endeavor. Every word of a legal document may have consequences. At least, we lawyers are trained to draft as if that were the case. Once again we hope that an aspect of Word that so engages lawyers will inform others who use the program at industrial strength.

In this series we will explore the methods, tools and issues relating to the collaborative drafting of documents. This review will include the tools and functions within Word that assist (and sometimes hinder) this process, as well as third party products that can extend Word’s capabilities. We will look beyond word processing to consider issues relating to document storage and tracking when sharing responsibility for document drafting. In that spirit, we will look especially at the newly sprouting Web enabled systems to support collaborative drafting.

As we begin to explore this topic within our legal context, it will often matter who is participating in the process of collaboration. Let’s distinguish between “cooperative collaboration,” where all those who share responsibility live within our physical or virtual walls (and would sit on the same side of the table at a physical or virtual meeting) and “adversarial review” among those with differing (and sometimes very much competing) interests.

We will try to answer the following questions:

What activities must be supported when drafting documents collaboratively?

How should these activities be different when the collaboration context is cooperative, and when it is reviewed by the opposing side?

Has the ability to electronically share our documents altered our activities in any way? Or do we consider sharing our documents electronically with outside parties as being ‘different’ at all?

How do tools for document comparison – the phase which identifies changes in document content – improve or hinder our process? What are the strengths and weaknesses of these tools? Are tools internal to Word better than third-party tools?

What do the third-party tools enable which internal Word functionality does not? What causes the document comparison process to break down? Once broken, how can it be fixed?

What are the differences between Word’s Track Changes, File Versions and Compare Documents features?

What techniques can be used to assure the identity of the persons who have worked on a document?

How does Word preserve evidence of the drafting process? What strategies can be used to avoid creating this information in the first place? When it is desired to include such information during drafting, how can it be cleaned out before delivery of a document?

How should documents be stored to promote successful collaboration and maintain a proper revision history? What capabilities are offered by the file system, enterprise-wide document management systems and Web-based collaboration systems? Where do Web-enabled on-line collaboration tools fit into the process – better still, when will they fit in?

We will begin answering these questions in the next column. For now, just realize how few years ago it was that we supported teams of proofreaders whose job it was to review paper copies of the original document against paper copies of the revised version. eyeballing any differences they found between the two. Indeed, the term “redline” was derived from the generation of hand-drawn underlines made using a red pencil or pen. Today, we electronically produce this compared or redlined result, accelerating our ability to review, then accept or decline, changes made between parties.

But we’re moving toward a new document processing arena: where the revision process occurs not between parties on paper, but between parties on-line. We expect nearly instantaneous, if not simultaneous access to documents as they are drafted. As connectivity barriers faced as few as three years ago become relics of the past, we struggle through the new and emerging issues surrounding the document collaboration task: Do we have the same word processing applications? Do we share the same comparison technologies? Which choices better provide for the client share moment, and which choices produce a high-maintenance relationship where successful sharing is elusive?

The exchange of paper drafts of documents created few of practice issues described above. While the arrival of word processing both accelerated and intensified the drafting process, other times, the freedom to make changes invited more frequent and involved revisions. The electronic exchange of documents, however, both creates opportunities for enhancement of the speed and thoroughness with which collaboration can be accomplished, and risks accidental or malicious change as well as intentional or unintentional exposure of the details of the development of a document draft.

One could hardly imagine a more fitting topic on which to practice collaborative drafting than the writing of this series. Thus, a collaborative drafting environment has been established, in which Sherry Kappel of Microsystems (www.microsystems.com) will share her expertise with Word, especially extensive experience in the art and agony of document comparison, and with the hazards of electronically sharing document content.

 

This 2000 article originally appeared in Office Watch.Subscribe to Office Watch free at http://www.office-watch.com/.

[Originally appeared 2000.]

We return to the series of Word of Law columns on collaboration in the creation and editing of Microsoft Word documents. These columns themselves are a collaboration between Bob Blacksberg and Sherry Kappel of Microsystems. The first three columns in this series appeared in Word of Law No. 29, No. 30 and No. 31.

The next questions we set out to address were:

How do tools for document comparison – the phase which identifies changes in document content – improve or hinder our process? What are the strengths and weaknesses of these tools? Are tools internal to Word better than third-party tools? What do the third-party tools enable which internal Word functionality does not? What causes the document comparison process to break down? Once broken, how can it be fixed?

What are the differences between Word’s Track Changes, File Versions and Compare Documents features?

This week’s column examines the tools internal to Microsoft Word. The following weeks’ columns will review the third-party tools that address these needs.

Before digging in to Microsoft’s Word’s tools, we need to review the role of document comparison in the collaboration process. It is, of course, essential to shared responsibility for document editing or review for participants to be aware of the changes made as a document evolves.

To help understand document comparison and the collaboration tasks related to it more thoroughly and consistently, it helps to connect these to the collaboration functions described in issues 29 and 30. To “Track,” (with a deliberate connection to the “Track Changes” function of Word) means that authors, editors or reviewers can highlight insertions, moves or deletions as they are made. Tracking may include identification the person who made the change and the time it was made.

To “Compare” means to mark and report the differences between a document as we have drafted it and as another person has edited it, whether or not the changes were “tracked” during editing.

Finally, we need a word for the automation of acceptance or rejection of changes in the text of a document made during the collaboration or review process. The Word help file entitles that function “Incorporate reviewers’ changes…” so “Incorporate” is a good title.

In issue 29, we distinguished between the collaboration that occurs among a cooperative group from the review that occurs during an adversarial situation. Tracking, when it works, fits the needs of cooperative collaborators. In adversarial situations, however, the use of the Track Changes feature in Word may expose more information about the drafting process than desired. In that posture, only the comparison functions may be appropriate.

Let’s review, then, the tools offered by Microsoft Word for Tracking, Comparison and Incorporation. On its face, Microsoft Word 97 and 2000 offers tools that support all of these functions. (We will not cover the “OnLine Collaboration” features at this point). Tracking is supported by the Track Changes feature. The Track Changes function, when turned on using Tools|Track Changes|Highlight Changes or by double clicking on the TRK section of the status bar, causes inserted text to be marked in a special color, based on the User Name set in Name field of the Tools|Options|User Information dialog. Deletions are colored and struck through. With this option turned on, a document can accumulate a set of markings for one or a series of editors or reviewers. Word permits these markings to be visible during editing or hidden. Track changes stores name field value set in the User Information with each insertion and deletion in the document, along with the date and time of the change. Word also stores in the binary file format the name values of every user who has edited the document, whether or not track changes has been enabled.

Comparison is supported by Compare Documents, found under the menu Tools | Track Changes | Compare Documents. This function allows a document to be automatically marked, whether or not Track Changes has been enabled, by executing an automatic comparison between the document open on the screen and another document retrieved during the process. Again, insertions are marked in a special color, and deletions struck through. In this case all of the change bear the name field value contained in User Information and the date and time on the computer that executed the comparison at the time it was executed.

Incorporation is supported by Word’s Accept or Reject Changes function (Tools| Track Changes| Accept or Reject Changes. If a document has been marked using the Track Changes feature, or if a comparison document has been created using the Compare Document feature, a user is supposed to be able to review the changes in context and accept or reject each of them in turn.

Word 97 and 2000 are supposed to expand the collaboration capabilities of Track Changes with the Merge Documents function (Tools|Merge Documents). If you’re an old Word user, you’ll fondly remember our abilities to take an existing Word document,and “Merge” it with the revised edition of itself, to produce a third document which integrated the differences between them both.

This “Merge Documents” functionality, however, was revised in Word 97/2000 when instead it became a facility for integrating comments and tracked revisions made into a document by multiple collaborators. As long as each of the documents submitted by collaborative parties maintains their differences from the ‘original;’ only through use of tracked revisions, the ‘merger’ takes place without a hitch. However, should someone make untracked changes to the document, the ability to merge revisions and annotations become compromised and some type of manual intervention is required to pick out the changes and reinsert them as appropriately-tracked revisions. The Merge Documents feature generates a resulting Word document which contains the total assemblage of comments and revisions made amongst collaborators, ready now for Incorporation..

The frequency with which the word “supposed” appears in this column suggests all is not well with Words built-in document comparison features. Not all changes can be tracked automatically. A simple example is the deletion of a table row or column, which causes a message to appear that such a change cannot be tracked. For a relative simple collaboration situation, such as two users marking light revisions on a document not very complex, the use of the Track Changes function during editing may be satisfactory. For complex documents, with a large load of changes, moves and replacements, the legibility and ease of editing of a document may be impaired by Track Changes. The Incorporation task can be very difficult to follow, especially if a document has been edited by a number of reviewers.

Microsoft Word’s Compare Documents function may be the least successful of any of these built-in functions. It is quite trivial to produce situations where the Compare Document function produces illegible or incorrect results. This is the legacy Word currently bears as the core routines which facilitate their comparison technologies were actually written and introduced at Word’s 2.0 revision. Since that time, these features have been minimally maintained, but they began to show their age as far back as Word 6.0. This latest round of binary file changes – Word 97/2000 – brought enhancements in Word these features may not even recognize, such as text boxes and graphics.

We complete this weeks column with a quote from the Legal Users Guide available on Microsoft’s web site. This can be found at http://officeupdate.microsoft.com/legal/track%20changes.htm:

IMPORTANT NOTE:Microsoft recommends that most law firms use a third party solution for document comparison, such as Lexis-Nexis’ CompareRite, or Workshare’s Deltaview. See the chapter on third party solutions for more information about these products. Microsoft Word’s compare documents features works on relatively simple documents that do not contain too much complex formatting. Because of the complex nature of most legal documents, Word’s compare documents feature does not produce as good a result as the third party products mentioned above. Microsoft is currently working to address this shortcoming, but in the meantime the third party solutions are recommended.

This 2000 article originally appeared in Office Watch. Subscribe to Office Watch free at http://www.office-watch.com/.