Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Word
application.errors
conversions
docmanagement
drawing.graphics
formatting.longdocs
international
internet.assistant
mail
mailmerge.fields
menustoolbars
newusers
numbering
oleinterop
pagelayout
printingfonts
setup.networking
spelling.grammar
tables
vba.addins
vba.beginners
vba.customization
vba.general
vba.userforms
web.authoring
word6-7macros
word97vba
  
 
date: Tue, 20 Nov 2007 17:05:12 -0000,    group: microsoft.public.word.oleinterop        back       


document.Merge() gives inconsistent results   
hello,

in office 2003, if you did

document1.Merge(document2)

it would report a line that is in document1 but not in document2 as 
inserted, and a line that is in document2 but not in document1 as deleted. 
i.e. it would assume that document1 is the "new" document and document2 is 
the "old" document.

in office 2007 it is almost always the other way round i.e. assumes 
document1 is the old and document2 is the new (AFAICR this is the same as 
previous versions of office before 2003 used to do)

no problem so far, I just detect in my application (c# .net 2.0 FWIW) which 
version of word I am connected to, and set the sense of the comparison 
accordingly

HOWEVER,  under office 2007, for some pairs of documents, I get the same 
result regardless of whether I call:

document1.Merge(document2) or
document2.Merge(document1)

I.E. word 2007 is "intelligently" deciding which is the "new" and which is 
the "old". from my experiments it does not seem that this has to do with the 
file time stamp or the 'last saved' property.

Does anyone know how word 2007 decides which is the newer document and if 
there is any way I can override it to force the sense of the comparison.

TIA

Andy
date: Tue, 20 Nov 2007 17:05:12 -0000   author:   Andy Fish

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us