A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Word » Tables
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Word 2002 mail merge into a table



 
 
Thread Tools Display Modes
  #1  
Old March 22nd, 2010, 08:56 PM posted to microsoft.public.word.tables
dmorin
external usenet poster
 
Posts: 2
Default Word 2002 mail merge into a table

I have a 12 column table where I'm merging data from a data source. The data
in the columns are variable length so word wrap is on. In a perfect world 16
lines would fit on the page but because the comments column could be very
wordy, the table may overflow to the next page (and usually does). The
overflowing is good but when the page breaks after the 16 lines, I am losing
the 17 line and start printing the next page with the 18 line information. I
have page headers and footers but removing them did not solve the problem.
If the total merged data is 50 lines, I lose the 17 and 34 lines, this is
consistent.
Ads
  #2  
Old March 22nd, 2010, 11:07 PM posted to microsoft.public.word.tables
Doug Robbins - Word MVP
external usenet poster
 
Posts: 8,239
Default Word 2002 mail merge into a table

Do you have any Next Record fields in there?

--
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, originally posted via msnews.microsoft.com

"dmorin" wrote in message
...
I have a 12 column table where I'm merging data from a data source. The
data
in the columns are variable length so word wrap is on. In a perfect world
16
lines would fit on the page but because the comments column could be very
wordy, the table may overflow to the next page (and usually does). The
overflowing is good but when the page breaks after the 16 lines, I am
losing
the 17 line and start printing the next page with the 18 line information.
I
have page headers and footers but removing them did not solve the problem.
If the total merged data is 50 lines, I lose the 17 and 34 lines, this is
consistent.


  #3  
Old March 23rd, 2010, 02:44 PM posted to microsoft.public.word.tables
dmorin
external usenet poster
 
Posts: 2
Default Word 2002 mail merge into a table

thank you for your response. I'm including a line from my table:

«Merge Record » «memname» «sin» «oowdate» «remarks» «preference» «memcsts»
«ossa» «tkt» «pcst» «otherorders» «Next Record»

all the table rows are the same and I do get my 16 rows properly populated
but the 17 goes missing and then 18-34 populate properly but the 35 goes
missing, etc.



"Doug Robbins - Word MVP" wrote:

Do you have any Next Record fields in there?

--
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, originally posted via msnews.microsoft.com

"dmorin" wrote in message
...
I have a 12 column table where I'm merging data from a data source. The
data
in the columns are variable length so word wrap is on. In a perfect world
16
lines would fit on the page but because the comments column could be very
wordy, the table may overflow to the next page (and usually does). The
overflowing is good but when the page breaks after the 16 lines, I am
losing
the 17 line and start printing the next page with the 18 line information.
I
have page headers and footers but removing them did not solve the problem.
If the total merged data is 50 lines, I lose the 17 and 34 lines, this is
consistent.


  #4  
Old March 23rd, 2010, 05:42 PM posted to microsoft.public.word.tables
Suzanne S. Barnhill
external usenet poster
 
Posts: 31,786
Default Word 2002 mail merge into a table

If this is set up as a label merge, then you don't want the «Next Record»
field in the first row. It would probably make more sense to set this up as
a catalog merge, which requires just one row (and no «Next Record» field at
all IIRC). Rereading your original post, though, I think the problem is the
spillover; if this is set up as a label merge, then each page is a separate
section, and the rows would ordinarily be set to an exact row height. Any
excess would be lost.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
http://word.mvps.org

"dmorin" wrote in message
...
thank you for your response. I'm including a line from my table:

«Merge Record » «memname» «sin» «oowdate» «remarks» «preference»
«memcsts»
«ossa» «tkt» «pcst» «otherorders» «Next Record»

all the table rows are the same and I do get my 16 rows properly populated
but the 17 goes missing and then 18-34 populate properly but the 35 goes
missing, etc.



"Doug Robbins - Word MVP" wrote:

Do you have any Next Record fields in there?

--
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, originally posted via msnews.microsoft.com

"dmorin" wrote in message
...
I have a 12 column table where I'm merging data from a data source.
The
data
in the columns are variable length so word wrap is on. In a perfect
world
16
lines would fit on the page but because the comments column could be
very
wordy, the table may overflow to the next page (and usually does). The
overflowing is good but when the page breaks after the 16 lines, I am
losing
the 17 line and start printing the next page with the 18 line
information.
I
have page headers and footers but removing them did not solve the
problem.
If the total merged data is 50 lines, I lose the 17 and 34 lines, this
is
consistent.




 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 03:35 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Copyright 2004-2018 OfficeFrustration.
The comments are property of their posters.