IncludePicture breaks in Word 2K3

[Tricia Turner]

I have upgraded a test machine from Word 2K to 2K3 and am having problems
with IncludePicture. I have a VB app that uses the Word object model to do a
mailmerge using a SQL Server datasource to a new document and that document
is then printed. One of the fields in the main doc has an IncludePicture
field that takes a mergefield as its parameter, i.e. { INCLUDEPICTURE "{
MERGEFIELD SomeImagePath }" }. When I used this in Word 2K this would pull
in the image from the mergefield, but when I do the same thing using 2K3
nothing is pulled in.

If I look at the value after merging to a new document it looks like {
INCLUDEPICTURE "\\\\SomeServer\\SomeDir\\image.tif" } which appears correct
but when I Alt+F9 the image does not display (no File. The strange thing is
that if I right-click the field and choose "Edit Field..." and choose OK on
the dialog box without changing any other value the field still looks
exactly the same as described above but now the Alt+F9 will pull in the
correct image.

Does anyone have any ideas about what might be causing this? Thanks!

 

[Peter Jamieson]

Does the picture display correctly if you select the field, F9, then Alt-F9
if necessary?

Generally speaking you have to check one or both of
Tools|Options|Print|Update fields and Update links, and/or select the
field(s) and execute the fields to ensure they are displayed.

Peter Jamieson

 

[Tricia Turner]

Thanks for the response Peter. The picture does display correctly if I
manually update the fields. I already have tried the various combinations of
checking the Update fields and Update links but it makes no difference. The
thing I don't understand is that it still works fine in 2000 as is. Besides
checking these two options is there anything that I can set either through
the Word UI or the Word object model that will automatically update these
fields? As I stated before, this is an automated app so I need to eliminate
user intervention.

 

[Peter Jamieson]

The general changes to do with link updating may be relevant - see

http://support.microsoft.com/default.aspx?scid=kb;en-us;330079

Other than that, I think the only thing you can do is modify your automated
app. so that it outputs to a new document and does at least

ActiveDocument.Fields.Update

and if necessary updates all fields in all storyranges.

Peter Jamieson .