FM 7.2 TOC LOT and LOF issue

[_Bharti_Telesoft_]

Whenever I generate a TOC or try to save an FM file after making any changes in it, it generates an error and does not save the changes.
Error: 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.

System preferences: Win XP, IBM PIV desktop, 504 MB RAM

[_Thomas_Michanek_]

The message tells you that while FM was saving your file, a problem with a graphic was encountered. So the obvious trouble-shooting
path is to go through the images you have imported into the document.

My bet is that you have imported graphics by copy, rather than by reference. That is, you copy and store a complete graphic into
your FM document rather than just referring to an external graphic file. This is a well-known cause for all sorts of problems, both
logistically and related to software bugs and performance. The problem becomes worse the more graphics of this type you have, the
larger the graphics are, and the more esoteric image formats you use.

If you _only_ use graphics imported by reference, the problem is probably related to disk or network problems. Try avoiding
referring to graphics stored in long, complex paths on other network drives, perhaps located externally to your office. Instead, try
to keep all graphics in a sub-folder to your document, or at least as "close" to your document as possible.
If you have all files on a local network drive, try copying them to your local disk. If they already are on your local disk, then
you might have a problem with your disk. Run a Disk Check and a Defragmentation of your local disk.

--
/Thomas Michanek

[Art Campbell]

Bharti,

Another possible problem than the path Thomas identified:

The errors that you're reporting are a common symptom related to having SP3 installed and having OLE objects in your FM files; maybe Visio drawings or Powerpoint slides or Excel spreadsheets.

This cropped up when SP3 was released as an OLE security fix, but Microsoft doesn't seem to have done anything about resolving it.

If this is your situation, the workarounds are to back out of SP3 or convert your OLE links to graphics or some other file format that can be imported by reference.

Art