M
mljames
I have a document that needs to be able to re-query it's merge
information without losing any changes that may have been made to th
non-merged parts. The initial merge is driven from Access with th
following code fragment:
Code
-------------------
With .ActiveDocument.MailMerge
.OpenDataSource Name:=CurrentDb.Name, ConfirmConversions:=False, _
ReadOnly:=True, linkToSource:=True, Connection:=strSource, _ ' strSource = "DSN=DSNName"
SQLStatement:=strDocQuery ' strDocQuery = "SELECT * FROM qryWordMerge WHERE ID = 5
.Destination = wdSendToNewDocument
.SuppressBlankLines = True
.Execute
End With
-------------------
I need Word (both 2000 and XP, with an option on 2003) to be able t
maintain the information about the link to Access so that when a use
re-opens the document, they will be prompted (or automatically) b
allowed to re-merge the data without going back to the template. Also
the solution needs to be flexible enough that I can set it up once an
efficiently pass it around the office to everyone else without havin
to do something on each machine.
If anyone has any ideas, I'd be very grateful!
Thanks,
Matt Jame
information without losing any changes that may have been made to th
non-merged parts. The initial merge is driven from Access with th
following code fragment:
Code
-------------------
With .ActiveDocument.MailMerge
.OpenDataSource Name:=CurrentDb.Name, ConfirmConversions:=False, _
ReadOnly:=True, linkToSource:=True, Connection:=strSource, _ ' strSource = "DSN=DSNName"
SQLStatement:=strDocQuery ' strDocQuery = "SELECT * FROM qryWordMerge WHERE ID = 5
.Destination = wdSendToNewDocument
.SuppressBlankLines = True
.Execute
End With
-------------------
I need Word (both 2000 and XP, with an option on 2003) to be able t
maintain the information about the link to Access so that when a use
re-opens the document, they will be prompted (or automatically) b
allowed to re-merge the data without going back to the template. Also
the solution needs to be flexible enough that I can set it up once an
efficiently pass it around the office to everyone else without havin
to do something on each machine.
If anyone has any ideas, I'd be very grateful!
Thanks,
Matt Jame