View Single Post
 
Old 09-18-2014, 08:50 PM
macropod's Avatar
macropod macropod is offline Windows 7 64bit Office 2010 32bit
Administrator
 
Join Date: Dec 2010
Location: Canberra, Australia
Posts: 22,365
macropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond reputemacropod has a reputation beyond repute
Default

In your original post, you said:
Quote:
The CSV file also has a field “SourceFile” which includes the complete file path and the file name
In that case, you should be able to use:
{IF {INCLUDEPICTURE {IF TRUE "{MERGEFIELD SourceFile}"} \d} {INCLUDEPICTURE {IF TRUE "{MERGEFIELD SourceFile}"} \d}}

Otherwise either of the following should work (I've tested & confirmed them):
{IF {INCLUDEPICTURE {IF TRUE "C:\\FPC_Directory\\{MERGEFIELD FileName}"} \d} {INCLUDEPICTURE {IF TRUE "C:\\FPC_Directory\\{MERGEFIELD FileName}"} \d}}
{IF {INCLUDEPICTURE {IF TRUE "C:\FPC_Directory\{MERGEFIELD FileName}"} \d} {INCLUDEPICTURE {IF TRUE "C:\FPC_Directory\{MERGEFIELD FileName}"} \d}}

As before, the field construction in your latest post looks OK, though there should be a space between the }{ pair, as in } {. The field codes I've represented above have all the unnecessary spaces removed.

When the merge using such fields is executed, your output file should have the images and no links. The only way I can generate a file with links with the above field code is by saving the merge preview.
__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]
Reply With Quote