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 » Mailmerge
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Mergefield nested in Includetext doesn't recognize path in WD2007



 
 
Thread Tools Display Modes
  #1  
Old July 22nd, 2009, 02:38 PM posted to microsoft.public.word.mailmerge.fields
WPenfold
external usenet poster
 
Posts: 5
Default Mergefield nested in Includetext doesn't recognize path in WD2007

Hi, I'm trying to convert some mailmerge documents to WD2007 and having a
problem with Includeext that is based on a Mergefield:

{IncludeText "{MergeField PARA_INTERVIEW}"}

Where PARA_INTERVIEW is H:\\interview.doc

Instead of including the file, the string: "H:\\interview.doc" is included
in the merged document instead. Yet if I highlight the string in the merged
document and press Shift F9, it does pull in the document, so it can
successfully find it, for some reason it just doesn't seem to recognize it as
a path in the original merge. Any suggestions how to deal with this? I've
tried every combination of double quotes and backslashes I can think of.
  #2  
Old July 22nd, 2009, 10:13 PM posted to microsoft.public.word.mailmerge.fields
Doug Robbins - Word MVP
external usenet poster
 
Posts: 8,239
Default Mergefield nested in Includetext doesn't recognize path in WD2007

Based on information from fellow MVP Macropod, if you use the following
field construction in the mail merge main document, the field will be
updated automatically:

{IF {INCLUDETEXT {IF TRUE "«PARA_INTERVIEW»"}} {INCLUDETEXT {IF TRUE
"«PARA_INTEVIEW»"}}}

You probably know that you must use Ctrl+F9 to insert each pair of field
delimiters {}

--
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
"WPenfold" wrote in message
...
Hi, I'm trying to convert some mailmerge documents to WD2007 and having a
problem with Includeext that is based on a Mergefield:

{IncludeText "{MergeField PARA_INTERVIEW}"}

Where PARA_INTERVIEW is H:\\interview.doc

Instead of including the file, the string: "H:\\interview.doc" is included
in the merged document instead. Yet if I highlight the string in the
merged
document and press Shift F9, it does pull in the document, so it can
successfully find it, for some reason it just doesn't seem to recognize it
as
a path in the original merge. Any suggestions how to deal with this?
I've
tried every combination of double quotes and backslashes I can think of.


  #3  
Old July 23rd, 2009, 01:38 AM posted to microsoft.public.word.mailmerge.fields
macropod[_2_]
external usenet poster
 
Posts: 2,402
Default Mergefield nested in Includetext doesn't recognize path in WD2007

Hi Doug,

If the OP doesn't need to break the links, all that's needed is:
{INCLUDETEXT {IF TRUE "«PARA_INTERVIEW»"}}

--
Cheers
macropod
[Microsoft MVP - Word]


"Doug Robbins - Word MVP" wrote in message ...
Based on information from fellow MVP Macropod, if you use the following field construction in the mail merge main document, the
field will be updated automatically:

{IF {INCLUDETEXT {IF TRUE "«PARA_INTERVIEW»"}} {INCLUDETEXT {IF TRUE "«PARA_INTEVIEW»"}}}

You probably know that you must use Ctrl+F9 to insert each pair of field delimiters {}

--
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
"WPenfold" wrote in message ...
Hi, I'm trying to convert some mailmerge documents to WD2007 and having a
problem with Includeext that is based on a Mergefield:

{IncludeText "{MergeField PARA_INTERVIEW}"}

Where PARA_INTERVIEW is H:\\interview.doc

Instead of including the file, the string: "H:\\interview.doc" is included
in the merged document instead. Yet if I highlight the string in the merged
document and press Shift F9, it does pull in the document, so it can
successfully find it, for some reason it just doesn't seem to recognize it as
a path in the original merge. Any suggestions how to deal with this? I've
tried every combination of double quotes and backslashes I can think of.



  #4  
Old July 23rd, 2009, 01:13 PM posted to microsoft.public.word.mailmerge.fields
WPenfold
external usenet poster
 
Posts: 5
Default Mergefield nested in Includetext doesn't recognize path in WD2

Great! I'll give it a try...

"macropod" wrote:

Hi Doug,

If the OP doesn't need to break the links, all that's needed is:
{INCLUDETEXT {IF TRUE "«PARA_INTERVIEW»"}}

--
Cheers
macropod
[Microsoft MVP - Word]


"Doug Robbins - Word MVP" wrote in message ...
Based on information from fellow MVP Macropod, if you use the following field construction in the mail merge main document, the
field will be updated automatically:

{IF {INCLUDETEXT {IF TRUE "«PARA_INTERVIEW»"}} {INCLUDETEXT {IF TRUE "«PARA_INTEVIEW»"}}}

You probably know that you must use Ctrl+F9 to insert each pair of field delimiters {}

--
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
"WPenfold" wrote in message ...
Hi, I'm trying to convert some mailmerge documents to WD2007 and having a
problem with Includeext that is based on a Mergefield:

{IncludeText "{MergeField PARA_INTERVIEW}"}

Where PARA_INTERVIEW is H:\\interview.doc

Instead of including the file, the string: "H:\\interview.doc" is included
in the merged document instead. Yet if I highlight the string in the merged
document and press Shift F9, it does pull in the document, so it can
successfully find it, for some reason it just doesn't seem to recognize it as
a path in the original merge. Any suggestions how to deal with this? I've
tried every combination of double quotes and backslashes I can think of.




 




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:38 PM.


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