Office 2003 Automation - Word Merge "loses" source

[M.C.]

Since I installed Office 2003, I have been experiencing
problems with a procedure in Access. It is supposed to
perform a query and then, using it as a database,
colonize merge fields in a predefined Word file. I keep
getting the message that the procedure cannot be executed
because it is NOT a merge file. I redid the merge file
in Word 2003, but it is not keeping its connection to the
source. It worked well with Office 2000. Anyone would
know what's happening? Any help appreciated.

 

[John Nurick]

Hi MC,

The Word mailmerge system changed significantly after Word 2000,
including, I believe, the object model. I haven't yet had to grapple
with the details, but I guess that this is what's causing the problem:
you may need to modify your Access procedure to reflect the change.

If you search http://groups.google.com I'm sure you'll find some
discussion of the issue in the Word newsgroups.