I had similar error messages with Frame files with OLE links to Excel
spreadsheets, but mostly randomly--sometimes I had the Excel file open by
mistake, and that might have triggered it, I'm not sure. I could never find
the exact cause. Was running Frame 7.1 on XP, SP2.

A colleague told me she got those errors all the time (same OLE links to
Excel files). She's going to be upgrading to Frame 8, but she's getting a
new computer as well, so there are too many variables there to narrow down
one cause if it ends up fixing her problem.

Have upgraded to Frame 8, still XP, SP2. Haven't had it that long, but I
haven't had any error messages so far. Doesn't mean that the upgrade fixed
the problem, though.

Using PDF's or graphics isn't a good fix for me, because we're linking to
parts lists that appear in the product manual and a separate parts book for
the entire product line. The advantage of OLE links to the Excel files is
that it's always linked to the latest and greatest version.

So thanks for the heads-up about SP3. I don't know if our IS dept. will be
rolling that out soon or not. Fortunately, I don't believe there are any
imminent plans to upgrade us to Vista.


On Fri, Jun 20, 2008 at 10:16 AM, Art Campbell <art.campbell at gmail.com>

> If you search back through the archives and/or visit the Frame user's
> forum on Adobe.com, you'll see that this has been a pretty common
> topic since Microsoft released SP3 for XP. They included some security
> fixes to OLE that have effectively broken it, at least as far as
> managing objects in Frame go.
> Only reported fix is backing out of SP3.
> Or you can convert the Visio objects to PDF, PNG, or other graphic
> files and import them by reference.
> May want to nag Microsoft some, if you think that would have an effect. ;-
> )
> Of course, if you're not using XP and haven't installed SP3, something
> else is at work, but I didn't see any system or FM version details in
> your post. Which would be important in solving the problem if it is
> something else.
> Art
> On Fri, Jun 20, 2008 at 10:35 AM, Brian Weis <bweis.wordsmith at gmail.com>
> wrote:
> > Yesterday, I encountered this error in FM:  "An internal error occurred
> > while writing imported graphics in this document. The file has been
> saved,
> > but has lost some image data. Please report this error to Adobe Technical
> > Support."
> >
> >
> > I close the error dialog, and then try to close the file ... but I am
> > prompted once again to save it before closing. I am now in a loop until I
> > break the cycle by clicking "No" in the save prompt. Contrary to the
> error
> > message's statement that the file has been saved, I find that none of my
> > changes, text or otherwise, are in the file. With a little more work, I
> am
> > able to determine that a Visio object must be the culprit.
> ....
> --
> 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
> _______________________________________________
> You are currently subscribed to Framers as rentagoodbook 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/rentagoodbook%40gmail.com
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.

Reply via email to