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 / November 2003

Tip: Looking for answers? Try searching our database.

Merging multiple docs using Includetext problems

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jigsatics - 05 Nov 2003 16:12 GMT
Hi!

I'm currently working on a project involving mail merge. Each person,
should have at least one establishment owned. For every establishment,
there will be a document sent to the client. I tried the If..Then..Else
statement using includetext to automatically attached all the necessary
documents for each person. This works but the only problem I
encountered is that it messes up my formatting. Why does it change the
formatting of the original document once it's used in an includetext?
How do I prevent this happening? It's so messed up that I find
bold-type words in the middle of a sentence whereas the original
doesn't have any.

I appreciate any help in solving this problem..

Thanks.

I forgot to mention that I'm using Word 97.
Cindy M  -WordMVP- - 05 Nov 2003 17:53 GMT
Hi Jigsatics,

> I'm currently working on a project involving mail merge. Each person,
> should have at least one establishment owned. For every establishment,
[quoted text clipped - 6 lines]
> bold-type words in the middle of a sentence whereas the original
> doesn't have any.

Does the field where this happens contain a \* MergeFormat switch, by any
chance? (Press Alt+F9 to see the field codes) If it does, try deleting
that and see if things settle down a bit...

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Sep 30 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :-)
Jigsatics - 07 Nov 2003 22:32 GMT
Yeah, it did.. I removed all of them and I still have the weird
formatting. Let me clarify the situation. The first page is a cover
letter created in Arial size 11 font. While the main part of the
questionnaire plus the sub-sections are all in Times Roman size 9. How
can I preserve this formats when I use an includetext?
Cindy M  -WordMVP- - 08 Nov 2003 21:01 GMT
Hi Jigsatics,

> Yeah, it did.. I removed all of them and I still have the weird
> formatting. Let me clarify the situation. The first page is a cover
> letter created in Arial size 11 font. While the main part of the
> questionnaire plus the sub-sections are all in Times Roman size 9. How
> can I preserve this formats when I use an includetext?

Ok, there are two issue, here. One is the \* Mergeformat switch problem.
Once that's been placed into a field, it can end up storing "weird"
formatting in the field where you can't always remove it. Safest would
be to copy the text within the field, press Ctrl+F9 to create a new pair
of field codes, paste it in, and delete the old field.

The other problem is how Word is designed to handle formatting. All text
in Word is formatted with STYLES. If you don't specify anything else,
this will be the style named "Normal". Or, you may have applied a
built-in or user-defined style. The important thing you need to know in
this case is, that Word will always apply the style definition in the
"container" document. So if the text coming through the link is
formatted with a style of the same name, it will take on the appearance
of the style as it is defined in the document where you're using
IncludeText.

You need to create a unique set of styles in the source document so that
Word will retain that formatting across the link.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Sep 30 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any follow question
or reply in the newsgroup and not by e-mail :-)
Jigsatics - 10 Nov 2003 17:58 GMT
> You need to create a unique set of styles in the source document so
> that
> Word will retain that formatting across the link.
>  

What do you mean by the source document? The main document with the
includetext statements? Or the sub-sections(the one's formatted in
times roman 9)?
Cindy M  -WordMVP- - 11 Nov 2003 13:35 GMT
Hi Jigsatics,

> > You need to create a unique set of styles in the source document so
> > that
[quoted text clipped - 4 lines]
> includetext statements? Or the sub-sections(the one's formatted in
> times roman 9)?

source document = document whose path is used in the IncludeText field.

Short summary: text formatted with styles of the same name will always
appear the same when combined in one document. In order to retain
formatting, text being brought in from an outside document must be
formatted with a style NAME that is not present in the target document
(the one containing the IncludeText field)

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Sep 30 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any follow question
or reply in the newsgroup and not by e-mail :-)
Jigsatics - 12 Nov 2003 21:11 GMT
Thanks Cindy!

It was the styles that caused the problem. Problem solved
Francis Dion - 11 Nov 2003 04:20 GMT
Hi,

You might want to investigate XpertDoc as an alternative to
IncludeText and MailMerge. XpertDoc has been specifically designed to
easily embedded If...Then...Else logic and other similar construct
into a merge project.

You can check it out at www.xpertdoc.com

Regards,

> Hi!
>
[quoted text clipped - 18 lines]
> ~~ Message posted from http://www.WordForums.com/
> ~~ View and post usenet messages directly from http://www.WordForums.com/
 
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.