INCLUDEPICTURE field in Word 2003
by Jose Valdes » Wed, 24 Jan 2007 02:35:42 GMT
Under some circumstances, linked (INCLUDEPICTURE field) graphics fail to
print (red X placeholder) even though they display fine on screen and
convert well to PDF. The problem graphics have one thing in common, I've
used Word's drawing utility (View -> Toolbars -> Drawing) to add a callout
or arrow. Unmodified graphics have no problem.
Steps to recreate problem
1. Insert drawing canvas (Insert->Picture->New Drawing).
2. Click inside drawing canvas.
3. Insert linked picture (Insert->Picture->From File and select Link to
File).
4. Display Drawing tool bar (View -> Toolbars -> Drawing).
5. Add an arrow or callout to drawing.
If there is no bug fix, I'm considering these workarounds:
Workaround 1 (frontrunner): Link only graphics that do not need to be
modified. For graphics that need callouts/arrows, use embedded graphics.
Word should run relatively fast in this scenario because I can cut the
number of embedded graphics in half.
Workaround 2: Use CorelDraw to add callouts/arrows to graphics, export from
CorelDraw, and link graphics in Word. This option is a lot of work when most
graphics only need a single arrow/callout. Also I haven't found an export
format (such as PNG, WMF, EMF, and EPS) that consistently works well in MS
Word (all graphics must display and print well in PDF). Also editing
graphics in CorelDraw significantly increases file size. Have not tried
Corel PHOTO-PAINT yet, but that's another option even though drawing
arrows/callouts is easier in drawing programs.
Workaround 3: Continue to link all graphics, but just live with the fact
that some graphics won't print from Word. That's painful, but workable.
Printing would require converting the book to PDF to avoid broken graphics.
In this workaround, I'd print less often because creating PDFs on my old
computer is agonizingly slow.
Re: INCLUDEPICTURE field in Word 2003
by Suzanne S. Barnhill » Wed, 24 Jan 2007 05:59:09 GMT
I expect Bob Buckland or someone else will be along in a bit to answer your
question, but I just wanted to compliment you on the clarity of your problem
description. It is rare to see a question so well *asked* in these NGs!
I might suggest one more possible workaround that would be worth an
experiment. I have been very pleased with the capabilities of SnagIt to add
arrows, callouts, and the like to graphics of all sorts. It can export in
quite a variety of graphic formats. A trial version is available from
www.techsmith.com.
--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://www.**--****.com/
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.
from
most
graphics.
Similar Threads:
1.Word 2003: put a field in an IncludePicture field
In Word 2003, I'd like my VBA code to create an IncludePicture field that
contains a field called "DOCPROPERTY home_directory" as part of the path to
the external graphic file.
Current line of code: Selection.InlineShapes.AddPicture fileName:=
"c:\Directory\file_name.jpg", LinkToFile:=True, SaveWithDocument:=False
Current result: { INCLUDEPICTURE "c:\\Directory\file_name.jpg" \*
MERGEFORMAT \d }
Desired result: { INCLUDEPICTURE "{ DOCPROPERTY
home_directory }\file_name.jpg" \* MERGEFORMAT \d }
Plan A that I am considering: allow the VBA code to create the link and do a
find/replace to change "c:\\Directory\file_name.jpg" to { DOCPROPERTY
home_directory }.
Plan B: find a DocProperty collection, assign home_directory to a variable,
and use variable in the AddPicture command.
Should I use Plan A or B? Or another plan? I know how to do A, but it seems
like the long way of solving the problem. I don't know whether plan B is
possible, but (if possible) it would require fewer lines of code. Any
thoughts?
2.Word 2003 INCLUDEPICTURE with Merge field inconsistant
I am using Word 2003 to Merge records from Excel 2003. I have an excel
column containing a Signature ID. In the merge document (Doc 1) I have
the following field:-
{INCLUDEPICTURE "C:\\Temp\\Sig_{ MERGERFILED SIG_ID }.bmp" \*
MERGERFORMAT }
Then the Doc 1 is merged to a new doc (Doc 2), all the output selected
and the fields updated with F9. This works correctly in Word 97 and
2000 but not in Word 2003.
In Word 2003 you get whatever was currently visible in Doc 1 displayed
throughout the Doc 2. If after opening Doc 1, I do not update the
field (leaving the image placeholder blank), Doc 2 has blank fields
throughout all records. If I step to record 3 in Doc 1, and update the
Signature field so that the correct signature for the record is
displayed, then the merged Doc 2 has record 3's signature throughout.
Just to confirm, if an identical document is created in Word 97 or
2000, the fields work perfectly.
Any Suggestions?
--
IanG
3.Word 2003 INCLUDEPICTURE with Merge field inconsistant.
I am using Word 2003 to Merge records from Excel 2003. I have an excel
column containing a Signature ID. In the merge document (Doc 1) I have the
following field:-
{INCLUDEPICTURE "C:\\Temp\\Sig_{ MERGERFILED SIG_ID }.bmp" \* MERGERFORMAT
}
Then the Doc 1 is merged to a new doc (Doc 2), all the output selected and
the fields updated with F9. This works correctly in Word 97 and 2000 but
not in Word 2003.
In Word 2003 you get whatever was currently visible in Doc 1 displayed
throughout the Doc 2. If after opening Doc 1, I do not update the field
(leaving the image placeholder blank), Doc 2 has blank fields throughout all
records. If I step to record 3 in Doc 1, and update the Signature field so
that the correct signature for the record is displayed, then the merged Doc
2 has record 3's signature throughout.
Just to confirm, if an identical document is created in Word 97 or 2000, the
fields work perfectly.
Any Suggestions?
4.Word changes file path inside {INCLUDEPICTURE} field code
5.Convert INCLUDEPICTURE text strings to Word fields with curly braces around the text string
6. Word 2003 - objects cannot be created from editing field code
7. INCLUDEPICTURE Field to use %Appdata%?
8. Auto-Refresh INCLUDEPICTURE Field in Mail Merge Document