I just upgraded from Office 2000 Pro to Office XP Pro. I have applied all
the patches for both Windows XP and Office XP.
I have several dozen MS Word mailmerge documents using a MS Access DB (on
the same computer, but different disk drive letter) as the data source. I've
been using these documents for several years and am very comfortable with
setup and use with these documents.
With Office XP Pro, when I open one of the mailmerge documents, I get the
following message "Opening this document will run the following SQL command:"
and then the select statement for the document is listed. The error also
states that data will be placed in the document and I'm asked if I want to
continue.
I never got this message in Office 2000 and I don't want it now. How can I
get the document to just open and automatically connect to the Access
database?
Unfortunatly, the problem doesn't stop there. If I click on the Yes button
in the above message box, i get a new message box stating that word cannot
find it's data source and gives me a dialog to find the data source . After
I find the Access database, all of the selection criteria is gone.
I redefine the selection criteria and the mailmerge process works correctly.
Even though I save the document, the next time I open it, I have to go
through the same process again.
This same problem occurs when I define a new document, using MS Word XP's
wizards.
How can I get this annowying process to stop.
Thanks,
Tom
Doug Robbins - 03 Aug 2005 04:56 GMT
See the following Knowledge Base article:
"Opening This Will Run the Following SQL Command" Message When You Open a
Word Document - 825765 at:
http://support.microsoft.com?kbid=825765

Signature
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
>I just upgraded from Office 2000 Pro to Office XP Pro. I have applied all
> the patches for both Windows XP and Office XP.
[quoted text clipped - 37 lines]
>
> Tom
Tom Sawyer - 03 Aug 2005 05:38 GMT
Doug,
Thank you very much. This solved my problem!
Tom
> See the following Knowledge Base article:
>
[quoted text clipped - 44 lines]
> >
> > Tom