[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Mike Tatro <tatro@xxxxxxx>, Jo Baer <jbaer@xxxxxxxxxxxxxxxxxxxx>, edunn@xxxxxxxxxxxxxxxxxxxxxxxx
Subject: RE: 2 Column Layout Problems
From: Thomas Neuburger <thomasn@xxxxxxxxxxxxxxxx>
Date: Tue, 08 Aug 2000 14:23:24 -0700
Cc: Framers@xxxxxxxxxxxxxx, Framers@xxxxxxxxx
In-Reply-To: <5D61B5891DE8D311B74200902746407F8CC4FD@epicenter.vsi.com>
Sender: owner-framers@xxxxxxxxx
For me it's been critical. I'm looking at an 8000+ pg docset, breaking 1000 pg books into smaller sets and making tables out of engineering-produced tabbed and bulleted lists in the process. I've never seen with so many tables in my life, and this internal error thing, once it starts, works like a clock. Ugh. Glad I didn't get hit with it two years ago. Tom Neuburger Mike Tatro wrote: >Thomas- > >I do believe this may be the first compelling reason I've heard to upgrade >to FM 6. > >Warmest Regards, >Michael L. Tatro >Documentation Manager >V-Systems, Inc. >tatro@vsi.com > > > -----Original Message----- > > From: Thomas Neuburger [mailto:thomasn@twelfthnight.com] > > Sent: Tuesday, August 08, 2000 10:21 AM > > To: Jo Baer; edunn@transport.bombardier.com > > Cc: Framers@FrameUsers.com; Framers@omsys.com > > Subject: Re: 2 Column Layout Problems > > > > > > Hi all, > > > > Re: the Internal Error message and tables in 5.5 -- From time > > to time you > > get this a lot. That is, with some documents, Frame 5.5 has tons of > > trouble, apparently when calculating table positioning in > > tables that break > > across pages. > > > > I've seen internal errors appear and disappear as the position of the > > bottom row of a split-page table moves up or down a few points due to > > editing. It's especially sensitive doing these calculations > > when the table > > has straddles. And chapters with many tables are suspect as well. > > > > It's clear that the table position mechanism is broken for > > tables that > > break across pages -- sometimes. You can spot the page the > > problem is on -- > > just watch as you page through. > > > > The good news is that every doc with a problem opens just > > fine in Frame 6. > > > > Sorry -- can't offer a solution. My answer was to go into > > Frame 6, fiddle > > with the table or the text above, and reopen in Frame 5 (customer > > requirement). Not a great solution if you don't have Frame 6, I know. > > > > Best, > > > > Tom Neuburger > > > > > > > > Jo Baer wrote: > > > > >It's possible that one or more of your tables is corrupted. > > I'd look first > > >for any > > >overrides to table properties, particularly keeping too many > > rows together > > >with the > > >"keep with next/previous" row format properties, or trying > > to keep the > > >table with a > > >preceding or subsequent paragraph if the table is too large. > > You might try > > >selecting > > >the table and reapplying the default table properties. > > > > > >Good luck, > > >Jo > > > > > >"To have a reason to get up in the morning, it is necessary > > to possess a > > >guiding > > >principle. A belief of some kind. A bumper sticker if you will." > > > > > > Judith Guest > > > > > >edunn@transport.bombardier.com wrote: > > > > > > > Has anyone else experienced problems using a 2-col layout > > with full width > > > > tables? > > > > That is, the tables are all the width of both columns. > > > > > > > > > > ** To unsubscribe, send a message to majordomo@omsys.com ** > > ** with "unsubscribe framers" (no quotes) in the body. ** > > ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **