Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Mailmerge and Fax / April 2007

Tip: Looking for answers? Try searching our database.

merge is pulling in every other record?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
andi - 24 Apr 2007 22:50 GMT
I've set up a mail merge doc in word for 6 labels/page and the formatting is
perfect - each label lines up right where I want it.  I am merging it with an
excel doc which has the data.  The weird thing is, when I do the merge, it is
pulling in every OTHER row of data.  So only half of my labels are printing.  
Does that ring a bell for anything obvious?  I can email the merge form if
necessary.  The form goes like this <<name>><<next record>> (second
line)<<table no.>> <<next record>>.  Help? Thank you!
Peter Jamieson - 24 Apr 2007 23:38 GMT
You should have one <<Next record>> before all the other fields on each
label, but no <<Next record>> in the first record on the page.

Peter Jamieson

> I've set up a mail merge doc in word for 6 labels/page and the formatting
> is
[quoted text clipped - 7 lines]
> necessary.  The form goes like this <<name>><<next record>> (second
> line)<<table no.>> <<next record>>.  Help? Thank you!
andi - 25 Apr 2007 00:10 GMT
Thanks for your help but that just made things worse.  Now it pulls in the
first name in the list twice, then skips 2, gets 3, skips 4, gets 5, skips 6,
gets 7, skips 8, gets 9 (that's 6 labels on the first page) - then repeats
that pattern when it goes to the next merged page (prints first label on
second page twice, skips next, etc.).  

> You should have one <<Next record>> before all the other fields on each
> label, but no <<Next record>> in the first record on the page.
[quoted text clipped - 12 lines]
> > necessary.  The form goes like this <<name>><<next record>> (second
> > line)<<table no.>> <<next record>>.  Help? Thank you!
Peter Jamieson - 25 Apr 2007 01:29 GMT
If you use Alt-F9 to show the field codes (so they look like { NEXT }, {
MERGEFIELD myfield } etc.)  do you see one { NEXT } at the beginning of each
label except the first? (sorry, I said record before when I meant label)?

If you select Table|Show Gridlines (In Word 2002/2003, not sure where it is
in Word 2007), does your table have an extra thin column between each
"label" column? Some label layouts are like that, and some just have one
column for each column of labels. But if you see the thin columns, do they
contain any fields? If so, get rid of them.

Finally, can you click the "pilcrow" button in the standard toolbar (it's
the one that looks like a fancy wrong-way-round "P"), to ensure that there
are no { NEXT } fields formatted as hidden text?

Peter Jamieson

> Thanks for your help but that just made things worse.  Now it pulls in the
> first name in the list twice, then skips 2, gets 3, skips 4, gets 5, skips
[quoted text clipped - 23 lines]
>> > necessary.  The form goes like this <<name>><<next record>> (second
>> > line)<<table no.>> <<next record>>.  Help? Thank you!
andi - 25 Apr 2007 13:36 GMT
Well, I feel like I'm getting closer but still problems.  Don't know if this
matters but I did find that my { NEXT } codes were After the merge fields,
not before so I moved all of them.  Also, one of the merge fields looked like
this:  { MERGEFIELD name } and the other had quotes { MERGEFIELD "table" }
The first two records (labels) merge fine - top left label, top right label.  
After that is where it skips to every other name on the data source.  Now
that I can see the page code - I also noticed that there is a funny little
character like a circle with four lines coming out from the four "corners"
(at 10/2/5/7 oclock) after each record AND outside the fine lines to the
right of the margin.  Is that just merge code?  Pulling my hair out on this
one.  I do merge docs all the time.  These are 175 place cards that at this
point, it would have been faster to just type in all the names and table
no's!!!  Any more ideas?  Let me know if I can email you both the word doc
and the excel spreadsheet for you to look at.  Thanks again for your time and
help on this.

> If you use Alt-F9 to show the field codes (so they look like { NEXT }, {
> MERGEFIELD myfield } etc.)  do you see one { NEXT } at the beginning of each
[quoted text clipped - 39 lines]
> >> > necessary.  The form goes like this <<name>><<next record>> (second
> >> > line)<<table no.>> <<next record>>.  Help? Thank you!
Peter Jamieson - 25 Apr 2007 13:56 GMT
Hi andi,

> Let me know if I can email you both the word doc
> and the excel spreadsheet for you to look at.

Yes, take "Killmap" out of my address and send them.

> this:  { MERGEFIELD name } and the other had quotes { MERGEFIELD "table" }

The quotes are only strictly necessary when the name has spaces or perhaps
other unusual characters.

> After that is where it skips to every other name on the data source.  Now
> that I can see the page code - I also noticed that there is a funny little
> character like a circle with four lines coming out from the four "corners"

These sound like the end-of-cell markers in your table (they are like
paragraph markers but, err..., mark end of cell. No need to worry about them
if so.

Peter Jamieson

> Well, I feel like I'm getting closer but still problems.  Don't know if
> this
[quoted text clipped - 73 lines]
>> >> > necessary.  The form goes like this <<name>><<next record>> (second
>> >> > line)<<table no.>> <<next record>>.  Help? Thank you!
andi - 25 Apr 2007 14:12 GMT
tried your addess minus the killmap (pjj at etc.) and it rejected saying
can't find a host named Spjjnet.demon.co.uk??

> Hi andi,
>
[quoted text clipped - 95 lines]
> >> >> > necessary.  The form goes like this <<name>><<next record>> (second
> >> >> > line)<<table no.>> <<next record>>.  Help? Thank you!
Peter Jamieson - 25 Apr 2007 14:35 GMT
Sorry andi, I should have said KillmapS

Peter Jamieson

> tried your addess minus the killmap (pjj at etc.) and it rejected saying
> can't find a host named Spjjnet.demon.co.uk??
[quoted text clipped - 126 lines]
>> >> >> > (second
>> >> >> > line)<<table no.>> <<next record>>.  Help? Thank you!
Peter Jamieson - 25 Apr 2007 23:11 GMT
This problem now solved after the documents were sent to me - too many {
NEXT } fields.

Peter Jamieson

> Sorry andi, I should have said KillmapS
>
[quoted text clipped - 132 lines]
>>> >> >> > (second
>>> >> >> > line)<<table no.>> <<next record>>.  Help? Thank you!
Doug Robbins - Word MVP - 25 Apr 2007 18:43 GMT
The funny little characters are just the end of cell markers and mean
nothing.  They will disappear if you click on the Show/Hide button (¶)

As Peter said in an earlier post if you toggle on the display of the field
codes by using Alt+F9, you should have the same mergefields in each label
(whether there are quote marks around the field name does not really matter,
and BEFORE the first Merge field in every label EXCEPT the first - something
like

{ MERGEFIELD name }                    |    { NEXT }{MERGEFIELD name }|
{NEXT }{ MERGEFIELD name }
{ MERGEFIELD table }                     |    { MERGEFIELD table }
|    { MERGEFIELD table }
_____________________________|_____________________________|_____________________________
{ NEXT }{ MERGEFIELD name }    |    { NEXT }{MERGEFIELD name }|
  {NEXT }{ MERGEFIELD name }
{ MERGEFIELD table }                     |    { MERGEFIELD table }
|    { MERGEFIELD table }
_____________________________|_____________________________|_____________________________

Signature

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

> Well, I feel like I'm getting closer but still problems.  Don't know if
> this
[quoted text clipped - 73 lines]
>> >> > necessary.  The form goes like this <<name>><<next record>> (second
>> >> > line)<<table no.>> <<next record>>.  Help? Thank you!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.