I have a unique problem. I am trying to use the INCLUDEPICTURE field code.
The document I'm using is linked to a very sophisticated database software
program and I have received instructions on merging data from this database
INTO the INCLUDEPICTURE field to create the filename for the photo files. An
example is typed below:

{INCLUDEPICTURE "G:\\START\\IMAGES\\PHOTOS\\{MERGEFIELD
"PROVIDER_LAST_NAME"}_{MERGEFIELD "PROVIDER_FIRST_NAME"}.GIF"}

In the above example, the photo filenames are all matched up to the fields
referenced in the formula (last_first.gif). These are the correct field
codes, and the double slashes are important, I have been told.

My problem is that as soon as I save the document containing the above
field, the underscores all change to "%20" and the field doesn't work!! No
one at my software vendor's help desk can help me with this problem. Does
anyone know anything about preventing this??

Thank you!

Cheryl

"Cheryl" wrote in message
...
I have a unique problem. I am trying to use the INCLUDEPICTURE field code.
The document I'm using is linked to a very sophisticated database software
program and I have received instructions on merging data from this
database
INTO the INCLUDEPICTURE field to create the filename for the photo files.
An
example is typed below:

{INCLUDEPICTURE "G:\\START\\IMAGES\\PHOTOS\\{MERGEFIELD
"PROVIDER_LAST_NAME"}_{MERGEFIELD "PROVIDER_FIRST_NAME"}.GIF"}

In the above example, the photo filenames are all matched up to the fields
referenced in the formula (last_first.gif). These are the correct field
codes, and the double slashes are important, I have been told.

My problem is that as soon as I save the document containing the above
field, the underscores all change to "%20" and the field doesn't work!! No
one at my software vendor's help desk can help me with this problem. Does
anyone know anything about preventing this??

Thank you!

Cheryl
I use a similar statement to include signatures on all our letters at work:
{ INCLUDEPICTURE "C:\\SIGS\\{MERGEFIELD FULLNAME }.jpg" }- and it works
fine.

Two possibilities spring to mind - I too had problems using GIF images
originally, try using BMP or JPG instead - from the MS KB:

"Many JPEG or GIF images contain complex formatting options such as
animations, sounds, or progressive displays. Word does not use these
options. To modify the picture so that it includes only those elements that
Word uses, use a picture editing program to save the picture in a simpler
format: . For a GIF graphic, lower the complexity to CIS GIF 87 or 87A
rather than GIF 89A.
. For a JPEG picture, save it in the "simple" or "baseline" format,
without any progressive redraw features"

Secondly you are enclosing your mergefields in extra quotation marks which
I don't think are needed as no spaces so you could use
{ INCLUDEPICTURE "G:\\START\\IMAGES\\PHOTOS\\{MERGEFIELD
PROVIDER_LAST_NAME}_{MERGEFIELD PROVIDER_FIRST_NAME}.JPG" }
Oh and the curly braces have to be entered using CTRL-F9 I'm sure you
already know...
HTH
Graham

Graham

%20 is usually inserted to replace a space and not an underscore. Replace
the underscores with %5F in the original field construction and see if that
effects an improvement.

{INCLUDEPICTURE "G:\\START\\IMAGES\\PHOTOS\\{MERGEFIELD
"PROVIDER%5FLAST_NAME"}%5F{MERGEFIELD "PROVIDER%5FFIRST%5FNAME"}.GIF"}

--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org



Cheryl wrote:
I have a unique problem. I am trying to use the INCLUDEPICTURE field
code. The document I'm using is linked to a very sophisticated
database software program and I have received instructions on merging
data from this database INTO the INCLUDEPICTURE field to create the
filename for the photo files. An example is typed below:

{INCLUDEPICTURE "G:\\START\\IMAGES\\PHOTOS\\{MERGEFIELD
"PROVIDER_LAST_NAME"}_{MERGEFIELD "PROVIDER_FIRST_NAME"}.GIF"}

In the above example, the photo filenames are all matched up to the
fields referenced in the formula (last_first.gif). These are the
correct field codes, and the double slashes are important, I have
been told.

My problem is that as soon as I save the document containing the above
field, the underscores all change to "%20" and the field doesn't
work!! No one at my software vendor's help desk can help me with this
problem. Does anyone know anything about preventing this??

Thank you!

Cheryl