I
Ivan Nue
I have a VB6 application that automates Word to perform mail merges
from data in a SQL Server database.
Well, to put it briefly, on my installation of Word XP and a new
installation of Word 2003 as soon as the mail merge document is opened
via automation, the <document>.MailMerge.MainDocumentType value
becomes wdNotAMergeDocument.
Now, this problem does not occur on the Word 97 installations
throughout the office, and it also does not occur on the unpatched
Word XP installations. Only my installations of Word XP and Word
2003, which have both been updated via Office Update. I don't know if
this is related, but it is the only link I have found.
This is a problem here because there are wdCatalog type merges that
are executed automatically as wdFormLetter merges, resulting in a lot
of wasted paper.
Why doesn't Word work and what should I do?
Thanks in advance,
Ivan Nue
from data in a SQL Server database.
Well, to put it briefly, on my installation of Word XP and a new
installation of Word 2003 as soon as the mail merge document is opened
via automation, the <document>.MailMerge.MainDocumentType value
becomes wdNotAMergeDocument.
Now, this problem does not occur on the Word 97 installations
throughout the office, and it also does not occur on the unpatched
Word XP installations. Only my installations of Word XP and Word
2003, which have both been updated via Office Update. I don't know if
this is related, but it is the only link I have found.
This is a problem here because there are wdCatalog type merges that
are executed automatically as wdFormLetter merges, resulting in a lot
of wasted paper.
Why doesn't Word work and what should I do?
Thanks in advance,
Ivan Nue