P
Peter Jamieson
Hi Steve,
Point one is that where you have «First_», if you click Alt-F9, you'll see
something like { MERGEFIELD First_ }. I think of the { MERGEFIELD First_ }
form as the "field code", the «First_» form as the "placeholder", the thing
you see when you preview the results as the "preview result" and the real,
final, as-merged result as the "field result". If you want to modify the
field code, replace it altogether or edit it when you see the "field code".
Don't try to edit the placeholder.
Point two is that if your merge has to deal with one person addressees, two
person addressees, etc. and you are using 1,2 and more records in the data
source to model that, things can get pretty difficult in the Mail Merge Main
Document. OTOH if in this instance your documents always deal with the same
number of people. If you can get the info. about those people into a single
data source record, so much the better (from a mailmerge point of view).
In this case, you could probably get away witth...
{ SET AFirst { MERGEFIELD First_ } }{ SET ALast { MERGEFIELD Last } }It was
a pleasure to have { REF AFirst } { REF ALast } and { NEXT }{ MERGEFIELD
First_ } { MERGEFIELD Last } with us...
{ REF AFirst } and { MERGEFIELD First_ } were a great asset to the
workshop...
(i.e. you only need one { NEXT }
All the {} need to be the special field code braces you can insert using
ctrl-F9, but all the other text can be typed in the usual way.
I hope that makes a bit more sense but if not, please try to spell out what
doesn't.
Peter Jamieson
Point one is that where you have «First_», if you click Alt-F9, you'll see
something like { MERGEFIELD First_ }. I think of the { MERGEFIELD First_ }
form as the "field code", the «First_» form as the "placeholder", the thing
you see when you preview the results as the "preview result" and the real,
final, as-merged result as the "field result". If you want to modify the
field code, replace it altogether or edit it when you see the "field code".
Don't try to edit the placeholder.
Point two is that if your merge has to deal with one person addressees, two
person addressees, etc. and you are using 1,2 and more records in the data
source to model that, things can get pretty difficult in the Mail Merge Main
Document. OTOH if in this instance your documents always deal with the same
number of people. If you can get the info. about those people into a single
data source record, so much the better (from a mailmerge point of view).
It was a pleasure to have «First_» «Last» and «Next Record»«First_» «Last»
with us...
And then I'd like to use a sentence like
«First_» and «Next Record»«First_» were a great asset to the workshop...
What I'm trying to achieve is a situation where the same First_ names
appear
in the two lines of text.
In this case, you could probably get away witth...
{ SET AFirst { MERGEFIELD First_ } }{ SET ALast { MERGEFIELD Last } }It was
a pleasure to have { REF AFirst } { REF ALast } and { NEXT }{ MERGEFIELD
First_ } { MERGEFIELD Last } with us...
{ REF AFirst } and { MERGEFIELD First_ } were a great asset to the
workshop...
(i.e. you only need one { NEXT }
All the {} need to be the special field code braces you can insert using
ctrl-F9, but all the other text can be typed in the usual way.
I hope that makes a bit more sense but if not, please try to spell out what
doesn't.
Peter Jamieson