MailMerge.MainDocumentType = wdNotAMergeDocument on Open

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ivan Nue - 20 May 2004 21:49 GMT

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

Reply to this Message

Peter Jamieson - 21 May 2004 10:29 GMT

This is probably because of the new security feature in Word XP SP3 and Word
2003 that pops up a dialog box asking you to confirm that it's OK to run an
SQL command. See

http://support.microsoft.com?kbid=825765

Signature

Peter Jamieson

> I have a VB6 application that automates Word to perform mail merges
> from data in a SQL Server database.
[quoted text clipped - 19 lines]
>
> Ivan Nue

Reply to this Message

Ivan Nue - 21 May 2004 16:58 GMT

That's it! Thank you so much.

I've been aware of the newsgroups for about 15 years, and I still
can't get over that such a good resource persists for free. It's a
beautiful thing.

Thanks again,

Ivan Nue

> This is probably because of the new security feature in Word XP SP3 and Word
> 2003 that pops up a dialog box asking you to confirm that it's OK to run an
[quoted text clipped - 25 lines]
> >
> > Ivan Nue

Reply to this Message