L
Les Mercer
My problem involves mailmerges that work under Win98 SE, Access 2000 SP3 and
Word 2000 SP3, but give problems under Win XP Professional 2002 SP1, Access
2002 SP3 and Word 2002 SP3. MSKB and Google have failed to come up with even
a mention of the problem, let alone a solution.
I have an Access table called MMSource that contains numerous records with a
field called LetterType.
I have several Word mail merge documents, L100.doc, L200.doc, L300.doc etc,
that use MMSource as their data source.
At this point, old and new versions work the same.
But when I introduce the filter into Word using "Edit recipient list" to
select, e.g., LetterType=100, the problem starts.
Providing you use the original documents that were created in Word 2000, all
still works as long as you do not have to amend the name or location of the
data source.
But if you change things, or create a new mail merge document from scratch
using Word 2002 the problem occurs.
The filter works... until you save and close the document. When you reopen
the document you then get the message "this is a mailmerge main document.
Word cannot find its data source".
Originally the Access DB was on a network drive, so in case it was a
permissions problem, I moved it to my C:, pointed the document to the new
location. The problem still occurs.
I added the following code in the hopes that it would give info when I
opened the document, but I got the "...this is a mailmerge main document.
Word cannot find its data source" message first, so it was no help.
Private Sub Document_Open()
MsgBox "activedocument.MailMerge.DataSource.Name=" & vbCrLf &
ActiveDocument.MailMerge.DataSource.Name
MsgBox "activedocument.MailMerge.DataSource.ConnectString=" & vbCrLf &
ActiveDocument.MailMerge.DataSource.ConnectString
MsgBox "activedocument.MailMerge.DataSource.QueryString=" & vbCrLf &
ActiveDocument.MailMerge.DataSource.QueryString
End Sub
I have created demo versions of Access 2000 and 2002 DBs and documents to
illustrate the bug that I can send if required (total 325KB unzipped)
Has anyone else experienced this problems, and what is the fix?
Thanks
Les Mercer
Word 2000 SP3, but give problems under Win XP Professional 2002 SP1, Access
2002 SP3 and Word 2002 SP3. MSKB and Google have failed to come up with even
a mention of the problem, let alone a solution.
I have an Access table called MMSource that contains numerous records with a
field called LetterType.
I have several Word mail merge documents, L100.doc, L200.doc, L300.doc etc,
that use MMSource as their data source.
At this point, old and new versions work the same.
But when I introduce the filter into Word using "Edit recipient list" to
select, e.g., LetterType=100, the problem starts.
Providing you use the original documents that were created in Word 2000, all
still works as long as you do not have to amend the name or location of the
data source.
But if you change things, or create a new mail merge document from scratch
using Word 2002 the problem occurs.
The filter works... until you save and close the document. When you reopen
the document you then get the message "this is a mailmerge main document.
Word cannot find its data source".
Originally the Access DB was on a network drive, so in case it was a
permissions problem, I moved it to my C:, pointed the document to the new
location. The problem still occurs.
I added the following code in the hopes that it would give info when I
opened the document, but I got the "...this is a mailmerge main document.
Word cannot find its data source" message first, so it was no help.
Private Sub Document_Open()
MsgBox "activedocument.MailMerge.DataSource.Name=" & vbCrLf &
ActiveDocument.MailMerge.DataSource.Name
MsgBox "activedocument.MailMerge.DataSource.ConnectString=" & vbCrLf &
ActiveDocument.MailMerge.DataSource.ConnectString
MsgBox "activedocument.MailMerge.DataSource.QueryString=" & vbCrLf &
ActiveDocument.MailMerge.DataSource.QueryString
End Sub
I have created demo versions of Access 2000 and 2002 DBs and documents to
illustrate the bug that I can send if required (total 325KB unzipped)
Has anyone else experienced this problems, and what is the fix?
Thanks
Les Mercer