Word Compare Fails With Track Changes ON

Question

4.00/5 (1 vote)

See more:

Hi Everyone,

I have created Word Application object as following.

MyWordApp = CreateObject("Word.Application")

MyWordApp.Documents.Open(Doc1)

With MyWordApp.ActiveDocument
    .SaveAs(OutDoc)
    .TrackRevisions = True
    .ShowRevisions = True
    .PrintRevisions = True
    .Compare(Doc2, , 1)
End With

It works fine ! But when Doc1 or Doc2 has Track Changes On and I compare them, I encounter "Command Failed" error.

Any solution to compare a Document that has Track Changes On ?

Posted 17-Mar-11 23:21pm

Sifar - 0

Add a Solution

Comments

Maciej Los 19-Mar-11 16:29pm

See here:
http://lifehacker.com/?_escaped_fragment_=247919/microsoft-word-tip--how-to-compare-two-documents-for-differences#!247919/microsoft-word-tip--how-to-compare-two-documents-for-differences

Maciej Los 7-Apr-11 16:19pm

OK, why are you enable TrackRevision before comparing documents?

See MS Help. Take a look at "IgnoreAllComparisonWarnings" variable.

Compare Method
See AlsoApplies ToExampleSpecificsDisplays revision marks that indicate where the specified document differs from another document.

expression.Compare(Name, AuthorName, CompareTarget, DetectFormatChanges, IgnoreAllComparisonWarnings, AddToRecentFiles)
expression Required. An expression that returns a Document object.

IgnoreAllComparisonWarnings Optional Variant. True compares the documents without notifying a user of problems. The default value is False.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)