Art Campbell wrote:
> The reference to SP3 that you mentioned... a security "fix" in SP3
> breaks objects imported with OLE. So those types of imports break.
> The other graphics are probably imported as files, by reference, and
> don't use OLE.
>
> The fix is to replace the OLE objects by
This post is from a colleague of mine.
I have a growing problem with imported images into FrameMaker 7.2.
I typically work off a network. A few months ago, I started getting an odd
message when I'd try to save files with images that are imported objects.
(These are files I've worked on for
The reference to SP3 that you mentioned... a security fix in SP3
breaks objects imported with OLE. So those types of imports break.
The other graphics are probably imported as files, by reference, and
don't use OLE.
The fix is to replace the OLE objects by converting them to graphics
and
The reference to SP3 that you mentioned... a security "fix" in SP3
breaks objects imported with OLE. So those types of imports break.
The other graphics are probably imported as files, by reference, and
don't use OLE.
The fix is to replace the OLE objects by converting them to graphics
and
This post is from a colleague of mine.
I have a growing problem with imported images into FrameMaker 7.2.
I typically work off a network. A few months ago, I started getting an odd
message when I'd try to save files with images that are imported objects.
(These are files I've worked on for
