Word 2003 always displays graphics as embedded objects

[Dave K.]

I have a user running Office 2003 and for some reason, every file she opens
that contains a graphic, the graphic is displayed as an embedded object.
Right now I have her pressing ctrl+shift+F9 to convert the object back to a
graphic. As you can imagine this is a pain. It also occurs when she creates
a new document. I have looked everywhere I can think of and cannot locate
where to change this back nor does she know what, if anything, she did.
Anyone else can open the same file and the graphics display correctly so I
know the issue is unique to her machine. I know I can always reinstall
Office 2003 which will correct it but I would like to know in the future how
to resolve this. Thanks in advance.

 

[Suzanne S. Barnhill]

Alt+F9 will toggle field codes.

 

[Dave K.]

Awesome. I just tried it and it worked perfectly. Thanks! I will have to
read up on Field Codes.

 

[Margaret Aldis]

Hi Dave

Toggling the field codes will change the display, but the file itself will
still contain those graphics as editable embedded objects rather than
bitmaps. That's generally unnecessary and is likely to cause file size and
potentially compatibility problems so you may want to look into how users
are inserting bitmaps.

 

[Tech Larson]

This is very helpful

Hi Dave

Toggling the field codes will change the display, but the file itself will
still contain those graphics as editable embedded objects rather than
bitmaps. That's generally unnecessary and is likely to cause file size and
potentially compatibility problems so you may want to look into how users
are inserting bitmaps.

 

[ecc_larson]

This is very helpful

Hi Dave

Toggling the field codes will change the display, but the file itself will
still contain those graphics as editable embedded objects rather than
bitmaps. That's generally unnecessary and is likely to cause file size and
potentially compatibility problems so you may want to look into how users
are inserting bitmaps.

 

[Jessi]

This has helped me so much!

Hi Dave

Toggling the field codes will change the display, but the file itself will
still contain those graphics as editable embedded objects rather than
bitmaps. That's generally unnecessary and is likely to cause file size and
potentially compatibility problems so you may want to look into how users
are inserting bitmaps.

 

[ecc_garner]

awesome

Hi Dave

Toggling the field codes will change the display, but the file itself will
still contain those graphics as editable embedded objects rather than
bitmaps. That's generally unnecessary and is likely to cause file size and
potentially compatibility problems so you may want to look into how users
are inserting bitmaps.

 

[ecc_koch]

This is very cooooool.

Hi Dave

Toggling the field codes will change the display, but the file itself will
still contain those graphics as editable embedded objects rather than
bitmaps. That's generally unnecessary and is likely to cause file size and
potentially compatibility problems so you may want to look into how users
are inserting bitmaps.

 

[ecc_larson]

This is helpful

Hi Dave

Toggling the field codes will change the display, but the file itself will
still contain those graphics as editable embedded objects rather than
bitmaps. That's generally unnecessary and is likely to cause file size and
potentially compatibility problems so you may want to look into how users
are inserting bitmaps.

 

[ecc_tobben]

:
This was very helpful!

Hi Dave

Toggling the field codes will change the display, but the file itself will
still contain those graphics as editable embedded objects rather than
bitmaps. That's generally unnecessary and is likely to cause file size and
potentially compatibility problems so you may want to look into how users
are inserting bitmaps.