On Tue, 6 Nov 2007 13:25:09 -0800, "Dan Vint" <dvint at bea.com> wrote:
>I have a process in which I run both Frame 6 and 7 documents through an >automated build. One step in this effort is to save all the files to MIF >and do some string replacements on the file, then save that result back >to Native form so I can print the documents. Note that is this case no >substitutions were made, so it is just a round tripping of the files >from MIF to Native. That has always worked flawlessly for every version of Frame I've used, which goes back to Frame 3 on SunOS... ;-) > As these files are saved back to Native (via FrameScript) I'm getting >the following error/warning from Frame: > <<SnagIt.jpg>> >This has occurred on 4 different books, not sure if they have been all >Frame 6 or not, but this last one is 6. One of the books we couldn't >track the problem down and had to rebuild it. The other 3 seem to all be >related to embedded OLE graphics. Is there some known problem with OLE >embedded graphics or an issue with saving from MIF back to Native? There shouldn't be. OLE objects are preserved in MIF just as any other imported graphics are. However, since they are embedded, and not referenced, they are subject to the same troubles as other embedded graphics, which includ potential loss of data if there's inadequate disk space for the temporary files Frame generates when saving them. Check your Windows system environment variables for the TMP and TEMP directories, and make sure the drive referenced in them is not close to full. Aside from that, one cross-check you could try is to use "Wash via MIF", which is a File-menu item added by the Mif2Go plugin. It works fine for both books and individual files in the demo version, which is free: http://www.omsys.com/dcl/download.htm You only need to install the plugin files, m2rbook.dll and m2gframe.dll. Wash works by saving as MIF, then reloading the MIF and saving as Frame binary. If you don't see the same problem there, you may want to check the FrameScript code to see what options you are using for the saves to MIF and to Frame binary. I don't know of a particular one that would have that effect, but it's not impossible... HTH! -- Jeremy H. Griffith, at Omni Systems Inc. <jeremy at omsys.com> http://www.omsys.com/