[C. Cunningham]

I am using Graham's individual merge add-in
(http://www.gmayor.com/individual_merge_letters.htm), and lately when I merge
to separate documents, it "scrambles" the records, is the best that I can
describe it.

E.G. - i have filtered my recipients list down to 12 people. I select merge
to new document, and select the field for my file names and process the
merge. It appears to be processing and then end with a run-time error, but
it appears that the files have been created. Only problem is that there are
not enough files. Only 6 files were created, named according to the first six
records, but in the first file is the merged info from records 1&2, in the
second file is the info from records 2, 3&4, in file three is the merged info
from records 5&6, etc...

This has happened now in several different instances (and to a couple of
different employees, on different computers), with at least 3 separate master
merge documents. The only common factor I can determine is that there are
section breaks and a table in each merge document.

Does anyone have any suggestions as to what is causing this error, or how we
can work around it?

(Based on Doug's suggestion from my post on 1/20/06, I've already modified
the code to open the new documents in print layout view, rather than "normal"
view, and based it off of a special template to preserve page border
settings -see post 11/8/06.)

System info:
I'm using Word 2003 SP3, operating on Windows XP Pro, Version 5.1.2600
Service Pack 2 Build 2600.
Data source is an Excel 2003 ServicePack3 spreadsheet.

Thanks!

[Graham Mayor]

It is actually Doug's add-in (with a few minor modifications of my own that
Doug has approved). I merely host the add-in on my web site. If Doug has
suggested specific mods to suit your requirement, he may remember what
issues were involved. He will no doubt be along later

--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org



C. Cunningham wrote:
I am using Graham's individual merge add-in
(http://www.gmayor.com/individual_merge_letters.htm), and lately when
I merge to separate documents, it "scrambles" the records, is the
best that I can describe it.

E.G. - i have filtered my recipients list down to 12 people. I
select merge to new document, and select the field for my file names
and process the merge. It appears to be processing and then end with
a run-time error, but it appears that the files have been created.
Only problem is that there are not enough files. Only 6 files were
created, named according to the first six records, but in the first
file is the merged info from records 1&2, in the second file is the
info from records 2, 3&4, in file three is the merged info from
records 5&6, etc...

This has happened now in several different instances (and to a couple
of different employees, on different computers), with at least 3
separate master merge documents. The only common factor I can
determine is that there are section breaks and a table in each merge
document.

Does anyone have any suggestions as to what is causing this error, or
how we can work around it?

(Based on Doug's suggestion from my post on 1/20/06, I've already
modified the code to open the new documents in print layout view,
rather than "normal" view, and based it off of a special template to
preserve page border settings -see post 11/8/06.)

System info:
I'm using Word 2003 SP3, operating on Windows XP Pro, Version 5.1.2600
Service Pack 2 Build 2600.
Data source is an Excel 2003 ServicePack3 spreadsheet.

Thanks!

[Doug Robbins - Word MVP]

In the first instance, I would suggest that you download the most recent
version of the add-in from Graham's website and see if the problem still
occurs with that.

--
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

"C. Cunningham" wrote in message
...
I am using Graham's individual merge add-in
(http://www.gmayor.com/individual_merge_letters.htm), and lately when I
merge
to separate documents, it "scrambles" the records, is the best that I can
describe it.

E.G. - i have filtered my recipients list down to 12 people. I select
merge
to new document, and select the field for my file names and process the
merge. It appears to be processing and then end with a run-time error,
but
it appears that the files have been created. Only problem is that there
are
not enough files. Only 6 files were created, named according to the first
six
records, but in the first file is the merged info from records 1&2, in the
second file is the info from records 2, 3&4, in file three is the merged
info
from records 5&6, etc...

This has happened now in several different instances (and to a couple of
different employees, on different computers), with at least 3 separate
master
merge documents. The only common factor I can determine is that there are
section breaks and a table in each merge document.

Does anyone have any suggestions as to what is causing this error, or how
we
can work around it?

(Based on Doug's suggestion from my post on 1/20/06, I've already modified
the code to open the new documents in print layout view, rather than
"normal"
view, and based it off of a special template to preserve page border
settings -see post 11/8/06.)

System info:
I'm using Word 2003 SP3, operating on Windows XP Pro, Version 5.1.2600
Service Pack 2 Build 2600.
Data source is an Excel 2003 ServicePack3 spreadsheet.

Thanks!

[C. Cunningham]

I removed my current add-in, replaced it with the latest version from the
website, and restarted my computer, just to be sure it was reset. I tried
the merge again and get the same result.... multiple records merging into one
file...

If I merge the current record only, it gives me the proper result of a
single record in a single file, but if I try it on all of the filtered
records, it gives me the problem described earlier.

To make matters even more complicated, i just tested another one of my merge
documents that also contains section breaks and tables, and it executes just
fine... *sighs* Any suggestions on what to test or change or what other
information I can give you to help me troubleshoot this issue? I've examined
the merge code in the problem documents over and over and over again, and
cannot come up with any logic as to what is happening...


"Doug Robbins - Word MVP" wrote:

In the first instance, I would suggest that you download the most recent
version of the add-in from Graham's website and see if the problem still
occurs with that.

[C. Cunningham]

I forgot to add that after the merge with the problem executes, i get a
Microsoft Visual Basic popup error box that says:
Run-time error '5941':
The requested member of the collection does not exist.

Continue End Debug Help
(with only the End and Help options available, the other 2 are grayed out,
and nothing happens but a blank gray box when clicking on the help buttom)

This error box does NOT show up when the merge executes properly from one of
the good merge documents.

"C. Cunningham" wrote:

I removed my current add-in, replaced it with the latest version from the
website, and restarted my computer, just to be sure it was reset. I tried
the merge again and get the same result.... multiple records merging into one
file...

If I merge the current record only, it gives me the proper result of a
single record in a single file, but if I try it on all of the filtered
records, it gives me the problem described earlier.

To make matters even more complicated, i just tested another one of my merge
documents that also contains section breaks and tables, and it executes just
fine... *sighs* Any suggestions on what to test or change or what other
information I can give you to help me troubleshoot this issue? I've examined
the merge code in the problem documents over and over and over again, and
cannot come up with any logic as to what is happening...


"Doug Robbins - Word MVP" wrote:

In the first instance, I would suggest that you download the most recent
version of the add-in from Graham's website and see if the problem still
occurs with that.

[Doug Robbins - Word MVP]

It must be something peculiar to that document. If you don't filter the
data source, what happens?

If you want to send me the mailmerge main document, and some data (or I can
cobble up a data source to match) I will take a look at it.

--
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

"C. Cunningham" wrote in message
...
I forgot to add that after the merge with the problem executes, i get a
Microsoft Visual Basic popup error box that says:
Run-time error '5941':
The requested member of the collection does not exist.

Continue End Debug Help
(with only the End and Help options available, the other 2 are grayed out,
and nothing happens but a blank gray box when clicking on the help buttom)

This error box does NOT show up when the merge executes properly from one
of
the good merge documents.

"C. Cunningham" wrote:

I removed my current add-in, replaced it with the latest version from the
website, and restarted my computer, just to be sure it was reset. I
tried
the merge again and get the same result.... multiple records merging into
one
file...

If I merge the current record only, it gives me the proper result of a
single record in a single file, but if I try it on all of the filtered
records, it gives me the problem described earlier.

To make matters even more complicated, i just tested another one of my
merge
documents that also contains section breaks and tables, and it executes
just
fine... *sighs* Any suggestions on what to test or change or what other
information I can give you to help me troubleshoot this issue? I've
examined
the merge code in the problem documents over and over and over again, and
cannot come up with any logic as to what is happening...


"Doug Robbins - Word MVP" wrote:

In the first instance, I would suggest that you download the most
recent
version of the add-in from Graham's website and see if the problem
still
occurs with that.

[C. Cunningham]

I tried it with a test copy of the data source with fewer records, and left
them unfiltered, and received the same result... multiple records merging
into one
file...

I've emailed you the merge doc and the test copy of the data source. Thanks
so much for looking at this!


"Doug Robbins - Word MVP" wrote:

It must be something peculiar to that document. If you don't filter the
data source, what happens?

If you want to send me the mailmerge main document, and some data (or I can
cobble up a data source to match) I will take a look at it.

--
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

"C. Cunningham" wrote in message
...
I forgot to add that after the merge with the problem executes, i get a
Microsoft Visual Basic popup error box that says:
Run-time error '5941':
The requested member of the collection does not exist.

Continue End Debug Help
(with only the End and Help options available, the other 2 are grayed out,
and nothing happens but a blank gray box when clicking on the help buttom)

This error box does NOT show up when the merge executes properly from one
of
the good merge documents.

"C. Cunningham" wrote:

I removed my current add-in, replaced it with the latest version from the
website, and restarted my computer, just to be sure it was reset. I
tried
the merge again and get the same result.... multiple records merging into
one
file...

If I merge the current record only, it gives me the proper result of a
single record in a single file, but if I try it on all of the filtered
records, it gives me the problem described earlier.

To make matters even more complicated, i just tested another one of my
merge
documents that also contains section breaks and tables, and it executes
just
fine... *sighs* Any suggestions on what to test or change or what other
information I can give you to help me troubleshoot this issue? I've
examined
the merge code in the problem documents over and over and over again, and
cannot come up with any logic as to what is happening...


"Doug Robbins - Word MVP" wrote:

In the first instance, I would suggest that you download the most
recent
version of the add-in from Graham's website and see if the problem
still
occurs with that.