They might be right at that. Word's table machinery got MUCH more complex
with W2000, precisely to deal with the issue of HTML tables which are
conceptually rather different from Word tables. As you might have discovered
already, Word tables get rather hairy (for automated processing) if you have
merged and split cells. HTML tables handle this in a completely different
way.

Creating a nested table is an reasonable work-around for some purposes: if
your table has one cell split into two columns, then in HTML all the *other*
rows have to take that into account when dealing with the corresponding cell
in that column (COLSPAN=2). This gets horribly messy if other rows have
splits and merges in other columns. The simpler alternative is to leave the
cell unsplit but to nest another table (one row, two columns) within it.

You can check the Table's Uniform property to see whether the table has any
such 'features'.




"Pat Garard" apgarardATbigpondPERIODnetPERIODau wrote in message
...
G'Day All,

The product I am using is OverDrive ReaderWorks.

Their support now tell me that the 'unusual' nesting is
sometimes carried out by Word during a 'Save As...'
to HTML format.

This means that the 'nesting' is often NOT found in
the DOC format........

(to be continued..........(maybe).)
--
Regards,
Pat Garard
Australia

______________________________________

"Pat Garard" apgarardATbigpondPERIODnetPERIODau wrote in message
...
G'Day All,

Is there a smart way to locate, within a long document, tables
and/or text boxes that happen to be 'nested'?

I am trying to create an MSReader eBook, and it falls over
because of nested tables or text boxes.
--
Regards,
Pat Garard
Australia

______________________________________