Hi there - I'm using an "Includetext" field to display the contents of a
second Word document within the footer of my main document. This second
document is simply a three column table with text - some bold, some normal -
inside it. All good so far. I had a number of issues with fonts changing
during mail merges but think that *\CHARFORMAT may, just may, have resolved
these. But, the text that is displayed in the merged document is all normal -
no bold text "survives" the merge.
Any ideas gratefully received!
Cheers
James

Charformat sets the formatting to that of the field. Try merging without the
switch.
Make sure that the styles in the source document and target documents match
so there is no conflict between the imported versions and the resident
versions or use unique style names so there is no potential for conflict.

--

Graham Mayor - Word MVP

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




James Spencer wrote:
Hi there - I'm using an "Includetext" field to display the contents
of a second Word document within the footer of my main document.
This second document is simply a three column table with text - some
bold, some normal - inside it. All good so far. I had a number of
issues with fonts changing during mail merges but think that
*\CHARFORMAT may, just may, have resolved these. But, the text that
is displayed in the merged document is all normal - no bold text
"survives" the merge.
Any ideas gratefully received!
Cheers
James

Hi James,

When you use INCLUDETEXT fields, the imported text takes on the style
attributes for in-common styles that appear in the target document. For
example, If both documents use the 'Normal' style, defined as Arial in the
source document and as Courier in the target document, the imported text
will be converted to Courier. The \*CHARFORMAT switch simply overrides all
style formatting of fonts by applying the formatting of the first letter of
the 'I" in INCLUDETEXT to the entire result. The \*CHARFORMAT switch has no
effect on paragraph formatting though.

Cheers


"James Spencer" wrote in message
...
Hi there - I'm using an "Includetext" field to display the contents of a
second Word document within the footer of my main document. This second
document is simply a three column table with text - some bold, some
normal -
inside it. All good so far. I had a number of issues with fonts changing
during mail merges but think that *\CHARFORMAT may, just may, have
resolved
these. But, the text that is displayed in the merged document is all
normal -
no bold text "survives" the merge.
Any ideas gratefully received!
Cheers
James

Thanks guys. If I remove the \*Charformat switch, the merged text carries
different font sizes and is bold at random places - even though the source
and IncludeText document have exactly the same font - strange. Did I mention
that the IncludeText merges the text into a table. Anyway, if I add the
\*Charformat switch, I lose the bold altogether but then at least the font is
consistent. Seems I'm scuppered either way !
James


"macropod" wrote:

Hi James,

When you use INCLUDETEXT fields, the imported text takes on the style
attributes for in-common styles that appear in the target document. For
example, If both documents use the 'Normal' style, defined as Arial in the
source document and as Courier in the target document, the imported text
will be converted to Courier. The \*CHARFORMAT switch simply overrides all
style formatting of fonts by applying the formatting of the first letter of
the 'I" in INCLUDETEXT to the entire result. The \*CHARFORMAT switch has no
effect on paragraph formatting though.

Cheers


"James Spencer" wrote in message
...
Hi there - I'm using an "Includetext" field to display the contents of a
second Word document within the footer of my main document. This second
document is simply a three column table with text - some bold, some
normal -
inside it. All good so far. I had a number of issues with fonts changing
during mail merges but think that *\CHARFORMAT may, just may, have
resolved
these. But, the text that is displayed in the merged document is all
normal -
no bold text "survives" the merge.
Any ideas gratefully received!
Cheers
James