FM8 crashing like it's Word

[Art Campbell]

Because an "embedded" Visio uses Microsoft's OLE linking to embed the
visio file and Microsoft broke the OLE code to Frame when it
introduced XP SP3 -- OLE in FM and a number of other applications was
disabled by the security fix -- you can find numerous posts in the
archives about this if you look. The remedy was to save the Visio
files as a supported graphic format and import those by reference.

FM redid the OLE linking in FM 9, and, I believe a second time in FM 10.

So if you want to embed Visios as objects, you should upgrade....
although most people don't really trust/use OLE because it's always
been flakey and not fully supported by Microsoft.

Art

Art Campbell
               art.campbell at gmail.com
  "... In my opinion, there's nothing in this world beats a '52
Vincent and a redheaded girl." -- Richard Thompson
                                                      No disclaimers apply.
                                                               DoD 358



On Sun, May 15, 2011 at 8:19 AM, Orly Zimmerman <orlyz at marvell.com> wrote:
> HI All,
>
> I have been struggling with this problem for a while too and always thought
> that I just did not have enough memory.
>
>
>
> In any case, now I have 3GB RAM and it still crashes too often.
>
> FM 8 (p.277) from the Adobe Technical Suite 1.0 on a laptop, Windows XP, 32
> bit system, 2.53 GHz CPU, 3 GB RAM – I did see an improvement (i.e. fewer
> crashes) when I moved from 2GB RAM to 3GB RAM, but FM still crashes too
> often.
>
>
>
> There are two types of crashes – one, apparently when there are obvious
> missing cross references – because there have been systematic crashes when
> opening/closing my Revision history chaps – which are always short chapters
> with no figures, but lots of x-refs (always in tables) and some are always
> hidden, due the nature of our books. I understand that there is a bug that
> reports these hidden x-refs in tables as unresolved when updating the book
> (as reported by the error log file). If I do a search for unresolved x-refs
> in my book, however, no unresolved x-refs are found.
>
>
>
> The other type of crash has to do with whether I have “embedded” visios –
> this apparently can drive FM crazy – although I’m not sure why. I try to
> save the visios with the latest Visio version I have on my laptop –assuming
> this will help for some reason.
>
>
>
> If all else fails, usually, a MIF wash solves the problem, so I have scripts
> to save all my book files as MIFs and save all the MIF’s back to FM.
>
>
>
> BR,
>
> Orly.
>
>
>
>
>
> _______________________________________________
>
>
> You are currently subscribed to framers as art.campbell at gmail.com.
>
> Send list messages to framers at lists.frameusers.com.
>
> To unsubscribe send a blank email to
> framers-unsubscribe at lists.frameusers.com
> or visit
> http://lists.frameusers.com/mailman/options/framers/art.campbell%40gmail.com
>
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.
>
>