[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: framers@xxxxxxxxxxxxxx, framers@xxxxxxxxx
Subject: Corrupt file??
From: smurphy@xxxxxxxxxxxxxxx
Date: Mon, 11 Oct 1999 15:09:57 -0500
Receipt-Requested-To: smurphy@softworkscc.com
Sender: owner-framers@xxxxxxxxx
Hi framers, My team is running into a problem that has us all stumped. I'm curious to know if anyone else has experienced this or has a solution. We're using FM 5.5.6 on Windows 95. We have a FM file that is part of a software user guide. The software runs on five different platforms, and the file has five (5) conditions for the five different platforms on which the software runs. There are a number of screen captures in the document that are placed in tables (special table format for graphics; one row containing the screen capture and the second row containing caption information). There are also tables that contain field descriptions for the dialog boxes that are in the screen captures. These are "normal" old tables, with a grid, etc. Problem: ---------- The document frequently causes FrameMaker to crash. Usually the problem arises just after the book has been generated (none of the other files in the book have this problem). As we scroll through the document, we get to a point where one of the tables (different ones at different times, it seems) -- the ones containing field descriptions -- trails off into gibberish, and the ruling lines stop appearing in the table. If you press PageDown or try to scroll further through the document, FrameMaker crashes with the usual "serious problem" message. You can avoid a crash by closing the file immediately, without trying to scroll any further. Another way to temporarily "fix" the file is to display it with all conditions showing, and then re-conditionalizing it for printing -- provided you don't re-generate the book containing the file. At least that seems to work most of the time. I've tried saving the file in MIF format and restoring it, but it hasn't helped. The only thing that distinguishes this file (as far as I can tell) is that it has a lot of tables. There is also a lot of conditional text in the document. I don't know why this would make the document crash, however. Anyone have any ideas?? Steve Murphy Senior Documentation Specialist Adobe Certified Expert/FrameMaker, Acrobat SOFTWORKS, Inc. 5845 Richmond Highway Alexandria, VA 22303 USA (703) 317-8879 smurphy@softworkscc.com ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **