Opening this will run the following SQL command

[WimDeBoeck]

First off, I know about the http://support.microsoft.com/kb/825765 on how to
work around this error message.

When I'm getting this error, it says the command it'll execute is empty.
Also even when I click "Yes", no datasource gets connected. Although this
seems right since the document were indeed made using some mail merge
features (the "Next record" field was insert to make it possible to jump to
the fields that needed to be filled in). However the document is finished now
and it still asks about wanting to connect. When I tried changing the
template to 'Normal.dot' instead of the template which holds all the "Next
record" fields, it won't show the error message anymore.

I'd like to know how I could change the original template of the file to
make sure it doesn't want to connect to the datasource anymore.

 

[Peter Jamieson]

There appear to be some new problems in this area following a recent update.

But if you do not need a data source, you can try the following for Word
2002/2003:
a. /open/ your template (.dot, .dotx, or .dotm) - i.e. in Wor'd File|Open,
locate the template in the file system and open it. You don't want to create
a new document based on it.
b. enable the Mail Merge toolbar (e.g. using View|Toolbars)
c. click the first button and select Normal Word Document
d. save the template

If it's Word 2007 or an earlier Word and you can't work out the equivalent
route, let us know.

 

[Doug Robbins - Word MVP]

In Word 2007, from the Mailings tab, click on Start Mail Merge and then on
the Normal Word Document item.

--
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

 

[WimDeBoeck]

Thank you for your reply, this indeed did the trick.

Is there a KB article on this "recent update" you talk about? I'd like to be
able to show to the people who had this problem that it was caused by an
update by Microsoft rather than something I changed myself.

 

[Peter Jamieson]

There's a KB article that describes the update at

http://support.microsoft.com/kb/950241

and this leads to a number of other security advisory articles etc.

However, I do not think you will see a point where these articles say "we
made change A to fix problem B and the effect is C"

(or even just "we made change A to fix problem B")