B
bill
I have an access database with which I do several mail merges using a
query as datasource. Everything was working quite smooth until one of
our staff upgraded to office 2003. The Access application still works
fine but, there is a problem with the word document. I created it in
Word 2000, and as long as the person opening it uses Word 2000, there
is no problem. However, when a user who has word 2003 opens the
document from a mail merge in Access, there is an error generated when
a merge is attempted stating that this is not a mail merge document.
The the document seems to lose its datasource and the fact that its a
merge document. All the mail merge buttons become greyed out. Im
wondering if there is some difference in the way merge documents should
be saved and executed in office 2003.When I open the document in word
2003, set it up as a merge document, open the data source, test it and
close, then reopen it, its as if its lost its data source and the fact
that it is a merge document.
This is baffling.
Any help would be appreciated.
Thanks,
Bill
query as datasource. Everything was working quite smooth until one of
our staff upgraded to office 2003. The Access application still works
fine but, there is a problem with the word document. I created it in
Word 2000, and as long as the person opening it uses Word 2000, there
is no problem. However, when a user who has word 2003 opens the
document from a mail merge in Access, there is an error generated when
a merge is attempted stating that this is not a mail merge document.
The the document seems to lose its datasource and the fact that its a
merge document. All the mail merge buttons become greyed out. Im
wondering if there is some difference in the way merge documents should
be saved and executed in office 2003.When I open the document in word
2003, set it up as a merge document, open the data source, test it and
close, then reopen it, its as if its lost its data source and the fact
that it is a merge document.
This is baffling.
Any help would be appreciated.
Thanks,
Bill