Images in RTF Documents Using Version 5.0...

[BSchuyler]

We've run into a situation at our office.  One of our analysts upgraded her version of EA from 4.51 Build 750 to version 5.00 Build 765 and is having trouble getting  images (diagrams) to display as part of the final RTF document.  She did not make any changes to her configuration setup between the old version of EA and the upgraded version.  We have looked at every possible location in EA in which to control image displays within RTF documents and everything looks like it should be producing the images.

We took the exact same model (located on a shared drive) and brought it up on another laptop which has EA 5.00 Build 765 and it produces the RTF document with images.  We're at a loss on how this can be happening.  

The analyst even changed output images file types and was able to get an image to be displayed when set as BMP, but the image was very grainy and hard to see.  Ultimately, she went back to version 4.51 Build 750 and can now produce the RTF documents with images (diagrams) as EMF types.  

Can anyone help out on this situation and provide some additional suggestions or is this a bug in the current release?  

Regards,

Bill

[mikewhit]

Given that 765 works OK a) for other people b) with the same model, is it possible that there's something different/broken about either your Windows or MS Office installation on the machine in question ?

I'm thinking about service pack level, different versions of DLL, for example, or some incompatibility that using the new EA makes manifest. (SysInfo might show something)

Although I'm not a great fan of people who say "try XXX" in answer to forum questions, you could try using Repair (whatever it's called for Office, think it's a Setup option) or Windows Update to ensure the offending machine(s) are not harbouring broken files.

I won't say "try 766" !

[davisford]

make sure that before you output the RTF, you have saved and closed all images in the editor.  I found a problem with this, and notified sparx, and supposedly it is fixed in the next release.