Re: mailmerge ends prematurely w/o error
- From: "Peter Jamieson" <pjj@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Aug 2007 17:27:05 +0100
Just an observation... my own experience of doing this kind of thing (which is rather outdated now) is that Word probably has at least one memory leak that will appear no matter how you split up a large merge. It may be worth trying to do multiple merges using a script that starts word, does the merge, closes word and so on, but that's not particularly easy either.
Unless you are having problems with specific .txt files...
Peter Jamieson
--
Peter Jamieson
http://tips.pjmsn.me.uk
"christopher.allen" <"at workscape.com"> wrote in message news:O4osh1l5HHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
I have Word VBA code that basically:
opens a main doc
for each *.txt
opens it as a datasource
mailmerges it
saves it
Adobe ConvertToPDF
closes it
next
Sometimes, the mailmerge ends prematurely without merging all the records. No indication at all of any problem. These are 500-record datasources, the first record being the header info.
What really bothers me is that sometimes it works, sometimes it doesn't. Sometimes it'll do this on smaller datasource files too. It occurs on the mailmerge, not the ConverToPDF, sometimes on the first datasource.
Anyone experienced this? I'll be happy to supply more details if you want.
Word 2000, Windows XP SP2. Also reproduced with Word 2003.
.
- Follow-Ups:
- Re: mailmerge ends prematurely w/o error
- From: christopher.allen
- Re: mailmerge ends prematurely w/o error
- References:
- mailmerge ends prematurely w/o error
- From: christopher.allen
- mailmerge ends prematurely w/o error
- Prev by Date: Re: Execute an INCLUDETEXT with a macrobutton?
- Next by Date: Re: Embedded SQL within VBA?
- Previous by thread: mailmerge ends prematurely w/o error
- Next by thread: Re: mailmerge ends prematurely w/o error
- Index(es):