Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Mail merg using INCLUDEPICTURE field

569 views
Skip to first unread message

Bill

unread,
Dec 21, 2002, 10:34:11 PM12/21/02
to
I created a merg file exported from FileMaker that contianes the path
information for an image. When using the mail merge feature in Word I
insert a INCLUDEPICTURE field within my document and then nest the
mail merge field (contianing the path) within the INCLUDEPICTURE
field. However it fails to show the image. I get an error message
telling me that "filename not specified."

Any suggestions would be appreciated.

John McGhie [MVP - Word]

unread,
Dec 22, 2002, 6:56:43 PM12/22/02
to
Generically, it's because Word strips all fields from a merged document and
replaces them with their current result. I have cross-posted this to the
Mail Merge group, where the good and learned folks know the work-around.

People, the OP is using Mac Word, but he hasn't bothered to tell us which
version. Assume Word 97...

This responds to microsoft.public.mac.office.word on 21 Dec 2002 19:34:11
-0800, bkef...@attbi.com (Bill):

All Spam blocked with SpamNet: a free download from http://www.cloudmark.com/

Please post all comments to the newsgroup to maintain the thread.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs
+61 4 1209 1410, mailto:jo...@mcghie-information.com.au

Graham Mayor

unread,
Dec 23, 2002, 4:10:10 AM12/23/02
to
That's not quite it - it is all a matter of translation of the field
information coming from the Filemaker data.
What *exactly* is the result of the mergefield without the INCLUDEPICTURE
bit?

It should produce
C:\path\filename.jpg
or better still
c:\\path\\filename.jpg
or
c:\path\filename
etc

What INCLUDEPICTURE wants to see is
{INCLUDEPICTURE "c:\\path\\filename.jpg"} though it will sometimes accept
{INCLUDEPICTURE "c:\path\filename.jpg"}

You must build your field to make use of the information coming from the
data to provide this end result thus for example
{IncludePicture "{Mergefield fieldname}"}
or
{IncludePicture "{Mergefield fieldname}.jpg"
or
{IncludePicture "c:\\path\\{Mergefield fieldname}"}
or whatever combination it takes to produce what the field expects. You can
then merge to a new document, select all (CTRL+A) and then update the fields
(F9) to show the correct pictures in their places.
Note when building fields by hand that the curly brackets are entered with
CTRL+F9 and not simply typed from the keyboard.

--
<>>< ><<> ><<> <>>< ><<> <>>< <>>< ><<>
Graham Mayor - Word MVP
E-mail gma...@mvps.org
Web site www.gmayor.dsl.pipex.com
Word MVP web site www.mvps.org/word
<>>< ><<> ><<> <>>< ><<> <>>< <>>< ><<>


"John McGhie [MVP - Word]" <jo...@mcghie-information.com.au> wrote in message
news:p3kc0vsontil04n4o...@4ax.com...

Paul Berkowitz

unread,
Dec 25, 2002, 12:23:18 PM12/25/02
to
On the Mac, that will probably be (untested)

Hard Disk:Path:To:File Name

and the adjustment

{ INCLUDEPICTURE "Hard Disk:Path:To:File Name" }

To see it as a field code, select the field text and press SHIFT + F9, or
see all field codes in the document by pressing OPTION + F9. (Probably
better here. Toggle off the same way.)

On the Mac, build field codes manually by entering COMMAND + F9 (not
control) to get the special curly brackets.


--
Paul Berkowitz
MVP Entourage

Please "Reply To Newsgroup" to reply to this message. Emails will be
ignored.

0 new messages