[scw-tzg]

I have an application that automates Word to run Mail Merge (C++, Word2003).
We expect that a template document will be provided that has been set up as a
mail merge form letter with a header file attached and NO data source. Upon
installation of security update (KB950241), the process fails when the
template file is opened and we're checking that it is a Main mail merge
document with header file attached -- it has been changed to a Normal doc. I
see that when I open the template manually, I get the error "Opening this
will run the following SQL command" with a blank line following as there is
no data source information. When I select No in response to "Do you want to
continue", the document ceases to be a mail merge document. And based on the
information in KB825765, I see this is what I can expect when the process is
automated; since I have DisplayAlerts set to no, No is assumed as the
response to the dialog.

It seems to me that this takes unattended automation of mail merge
completely out of the picture, unless I have all my clients set up the
Registry hack (workaround) that essentially undoes the security update. And
what kills me is that I don't have a data source attached in the first place!


Can anyone recommend any solution other than applying the Registry
workaround? One thing I can consider is to apply this registry change
programmatically when I am about to open the template document, then remove
it when I am done with the merge. At least that leaves the security solution
intact any other time Word is used on the machine. Any comments?

[Doug Robbins - Word MVP]

You could start with a template that is a normal Word document and then, a
new document is created from the template, use Code to convert it to a mail
merge main document and attach the header and data sources.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"scw-tzg" susan 1DOT wolitz AT trizetto 1DOT com wrote in message
...
I have an application that automates Word to run Mail Merge (C++,
Word2003).
We expect that a template document will be provided that has been set up
as a
mail merge form letter with a header file attached and NO data source.
Upon
installation of security update (KB950241), the process fails when the
template file is opened and we're checking that it is a Main mail merge
document with header file attached -- it has been changed to a Normal doc.
I
see that when I open the template manually, I get the error "Opening this
will run the following SQL command" with a blank line following as there
is
no data source information. When I select No in response to "Do you want
to
continue", the document ceases to be a mail merge document. And based on
the
information in KB825765, I see this is what I can expect when the process
is
automated; since I have DisplayAlerts set to no, No is assumed as the
response to the dialog.

It seems to me that this takes unattended automation of mail merge
completely out of the picture, unless I have all my clients set up the
Registry hack (workaround) that essentially undoes the security update.
And
what kills me is that I don't have a data source attached in the first
place!


Can anyone recommend any solution other than applying the Registry
workaround? One thing I can consider is to apply this registry change
programmatically when I am about to open the template document, then
remove
it when I am done with the merge. At least that leaves the security
solution
intact any other time Word is used on the machine. Any comments?