View Single Post
  #3   Report Post  
Posted to microsoft.public.word.mailmerge.fields
Matt
 
Posts: n/a
Default wdSendToNewDocument Work around

Doug,

I really wish I could ingnore that guy, but unfortunately they're pointing
the finger at me. They say there are more people using their software with
the .dot than are using my db/mail merge, so I've gotta make changes. Do you
know of any other way to automerge? (other than wdSendToNewDocument)

-Matt

"Doug Robbins - Word MVP" wrote:

I would not accept the word of an "IT" guy that said that. However, if the
users need to be able merge to a new document then the IT guy should do his
job and sort out the problem.

If by chance there is some add-in that is causing the problem, select
Templates and Add-ins from the Tools menu and uncheck anything that it there
and see if that overcomes the problem.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

"Matt" wrote in message
...
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