Another table jumping; have I found a bug/feature?

[Avraham Makeler]

Since this comes hot on the heels of the previous table jumping thread, I
thought I would share this one, although I seem to have found some sort of
'solution', but maybe somebody could explain to me why this is happening.
I have this small table, which certainly fits on one page, that prefers
jumping to the next page. I found no 'problem' with any of the table rows
that should cause this. I put the table anchor on the table caption line. I
see that the "Keep With Next" of the table caption is set to true (to the
credit of the original author of this doc - not me). On all the table rows,
'Keep With Next' is set to false (no heading row), which is also correct.

So I decided to see what would happen if I set the caption's 'Keep With
Next' to false.
Lo and behold ... the table repositions itself to where it is supposed to
be.

Tentative conclusion: it seems that the setting:

"Keep With Next" = true

of the table caption (or maybe of the table anchor on that line) is
percolating down through all the table rows even though they themselves have
that setting set to false.

Comments, anyone?

avi


On Wed, Feb 11, 2009 at 7:09 PM, Avraham Makeler <amakeler at gmail.com> wrote:

>
>
> On Wed, Feb 11, 2009 at 6:59 PM, Avraham Makeler <amakeler at gmail.com>wrote:
>
>> Ok, end of mystery. Found the problem: I only just noticed that the Table
>> Designer also has an Orphan Rows field. The TableCaption style was set to
>> 99.
>> Thanks again to all.
>>
>>  - avi
>>
>>
>>
>> On Wed, Feb 11, 2009 at 12:37 AM, Combs, Richard <
>> richard.combs at polycom.com> wrote:
>>
>>> Avraham Makeler wrote:
>>>
>>> > I have a table where the whole table jumps to start at the page that
>>> > follows
>>> > the table's insertion page, so leaving a blank page. So the table's
>>> anchor
>>> > point is left at the top of the blank page, and the actual table
>>> itself
>>> > starts at the top of the next page.
>>> >
>>> > What is going wrong?
>>>
>>> Numerous possibilities. Check these:
>>>
>>> -- In Table Designer, Basic tab, is Start set to Top of Page (or
>>> something else causing the same outcome)?
>>>
>>> -- In the same place, is Orphan Rows set to a number too high to allow
>>> the table to break across pages?
>>>
>>> -- For each row, select Table > Row Format. Check the row's Start Row
>>> and Keep With settings.
>>>
>>> -- In addition, look for possible interactions of these settings. For
>>> instance, as others noted, a row can't break across pages. If you row 3
>>> is too tall to fit on the first page, but rows 1 and 2 are set to Keep
>>> With Next, or Orphan Rows is set to 3, then FM has to pull the whole
>>> thing down a page to conform to the settings.
>>>
>>> HTH!
>>> Richard
>>>
>>>
>>> Richard G. Combs
>>> Senior Technical Writer
>>> Polycom, Inc.
>>> richardDOTcombs AT polycomDOTcom
>>> 303-223-5111
>>> ------
>>> rgcombs AT gmailDOTcom
>>> 303-777-0436
>>> ------
>>>
>>>
>>>
>>>
>>>
>>>
>>
>