[stephen]

We like to encourage our users to always link to the original Visio file
(Insert Object... and select link) but it was pointed out to me that the
quality when printing (Mostly HP machines using either PCL or Postscript
drivers) is much better when pasted directly in (not as a metafile or other
image file, both are considered Visio objects and can be edited)....what
gives? Does anybody know the difference in this case between Pasting a visio
object versus inserting it?

Frustrated,

Stephen

[Cindy M.]

Hi ?B?U3RlcGhlbg==?=,

We like to encourage our users to always link to the original Visio file
(Insert Object... and select link) but it was pointed out to me that the
quality when printing (Mostly HP machines using either PCL or Postscript
drivers) is much better when pasted directly in (not as a metafile or other
image file, both are considered Visio objects and can be edited)....what
gives? Does anybody know the difference in this case between Pasting a visio
object versus inserting it?

Difficult to say... Make sure two such objects are formatted graphically "in
line with text". Press Alt+F9 to view the field codes behind the links and
compare them. Are the codes the same, or do they differ?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)

[stephen]

"Cindy M." wrote:

Hi ?B?U3RlcGhlbg==?=,

We like to encourage our users to always link to the original Visio file
(Insert Object... and select link) but it was pointed out to me that the
quality when printing (Mostly HP machines using either PCL or Postscript
drivers) is much better when pasted directly in (not as a metafile or other
image file, both are considered Visio objects and can be edited)....what
gives? Does anybody know the difference in this case between Pasting a visio
object versus inserting it?

Difficult to say... Make sure two such objects are formatted graphically "in
line with text". Press Alt+F9 to view the field codes behind the links and
compare them. Are the codes the same, or do they differ?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)

Cindy,

Thanks for the response.

The field codes are different.

The field code for the image that was inserted as an OLE object is
{LINK Visio.Drawing.11 "C:\AbsolutePathToFile\Image.vsd" "" \a \f 0 \p}

The field code for the pasted file is
{EMBED Visio.Drawing.11}

Any thoughts?

Thanks again,

Stephen

[Cindy M.]

Hi ?B?U3RlcGhlbg==?=,

We like to encourage our users to always link to the original Visio file
(Insert Object... and select link) but it was pointed out to me that the
quality when printing (Mostly HP machines using either PCL or Postscript
drivers) is much better when pasted directly in (not as a metafile or other
image file, both are considered Visio objects and can be edited)....what
gives? Does anybody know the difference in this case between Pasting a visio
object versus inserting it?

Difficult to say... Make sure two such objects are formatted graphically "in
line with text". Press Alt+F9 to view the field codes behind the links and
compare them. Are the codes the same, or do they differ?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)

Cindy,

Thanks for the response.

The field codes are different.

The field code for the image that was inserted as an OLE object is
{LINK Visio.Drawing.11 "C:\AbsolutePathToFile\Image.vsd" "" \a \f 0 \p}

The field code for the pasted file is
{EMBED Visio.Drawing.11}

Any thoughts?

In the first case, you still have an active OLE link back to Visio, as a *.vsd file.
In the second case, the Visio drawing is "simply" being embedded into the document
without an active link back to the Visio application. In this case, Word's "engine"
is interpreting how the object will look and print, rather than Visio's.

As a general rule, your documents will be faster and "lighter" NOT using the LINK
field, as this will embed a portion of the OLE Server (Visio) in the Word document.
For some graphics objects, one actually gets a *better* result by doing this. In
your case, however, the quality is apparently better when Visio is not involved in
the rendering. So I'd go with the users who do not use Insert/Object :-)

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply in
the newsgroup and not by e-mail :-)

[stephen]

In the first case, you still have an active OLE link back to Visio, as a *.vsd file.
In the second case, the Visio drawing is "simply" being embedded into the document
without an active link back to the Visio application. In this case, Word's "engine"
is interpreting how the object will look and print, rather than Visio's.

As a general rule, your documents will be faster and "lighter" NOT using the LINK
field, as this will embed a portion of the OLE Server (Visio) in the Word document.
For some graphics objects, one actually gets a *better* result by doing this. In
your case, however, the quality is apparently better when Visio is not involved in
the rendering. So I'd go with the users who do not use Insert/Object :-)

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply in
the newsgroup and not by e-mail :-)


Cindy,

That explains that. Thanks again for your assistance.

Stephen