M
Matt
I've got a bunch of merge documents that use:
..Destination = wdSendToNewDocument
in thier auto-merge macro:
Sub Startup()
Dim DocName$
DocName = ActiveDocument.Name
With ActiveDocument.MailMerge
.Destination = wdSendToNewDocument
.Execute
End With
Windows(DocName).Close wdDoNotSaveChanges
End Sub
The problem is that there are a few users of the merge documents that have a
special software on their computers that uses a customized .dot file. This
file overrides the .Destination = wdSendToNewDocument command in my script.
(according to an IT guy here)
These users can merge the documents, but they cannot save or print the
documents (print can be achieved via print preview). Even a copy/paste of the
merged doc to a new word doc yields the same results.
On all other computers not using the software/.dot file, there are no
problems.
Is there a command I can use that does the same thing as .Destination =
wdSendToNewDocument?
Thanks in advance,
-Matt
..Destination = wdSendToNewDocument
in thier auto-merge macro:
Sub Startup()
Dim DocName$
DocName = ActiveDocument.Name
With ActiveDocument.MailMerge
.Destination = wdSendToNewDocument
.Execute
End With
Windows(DocName).Close wdDoNotSaveChanges
End Sub
The problem is that there are a few users of the merge documents that have a
special software on their computers that uses a customized .dot file. This
file overrides the .Destination = wdSendToNewDocument command in my script.
(according to an IT guy here)
These users can merge the documents, but they cannot save or print the
documents (print can be achieved via print preview). Even a copy/paste of the
merged doc to a new word doc yields the same results.
On all other computers not using the software/.dot file, there are no
problems.
Is there a command I can use that does the same thing as .Destination =
wdSendToNewDocument?
Thanks in advance,
-Matt