I tried doing your instructions and WORD insists that it cannot understand the command and throws out the field on a merge. In my test document I used three fields; firstname, lastname, and picturefile as the field names. I typed in your example carefully, it loks like this:
«Field_1» «Field_2» {INCLUDEPICTURE "c:\\working\\uha\\ {MERGEFIELD picturefile }" } where the curly braces came from using <ctrl>F9 . Word just pukes and throws the whole includepicture thing out.
--
We get too soon old and too late smart.
> You should be able to use an { INCLUDEPICTURE } field. If by "reference
> listing" you mean that you have the name of the picture file in a field
[quoted text clipped - 13 lines]
> way to use a reference listing ("picture1.jpg") instead of the actual
> picture?
> Word just pukes and throws the whole includepicture thing out.
What message does Word actually display? What if you plug in the name of the
jpg file directly instead of the {MERGEFIELD picturefile } field?
As it happens there is a space in
{INCLUDEPICTURE "c:\\working\\uha\\ {MERGEFIELD picturefile }"
just before the {MERGEFIELD
If the space is there in the nested field that you typed and not just in
your message, delete it and try again.

Signature
Peter Jamieson
> I tried doing your instructions and WORD insists that it cannot understand the command and throws out the field on a merge. In my test document I used
three fields; firstname, lastname, and picturefile as the field names. I
typed in your example carefully, it loks like this:
> ?Field_1? ?Field_2? {INCLUDEPICTURE "c:\\working\\uha\\ {MERGEFIELD
picturefile }" } where the curly braces came from using <ctrl>F9 . Word
just pukes and throws the whole includepicture thing out.
> --
> We get too soon old and too late smart.
[quoted text clipped - 16 lines]
> > way to use a reference listing ("picture1.jpg") instead of the actual
> > picture?