Same here. I always work in 'Page View'. My largest table right now is 
apprx. 130 pages - set up in A4 - not US Letter... No problems with page 
breaks. My tables consists of 2 or 3 columns.

But I have noticed one big thing working with such large tables. NWP 
gets extremely slow when exceeding 100 pages with text only tables.

A work-around for this is to make such large tables into 'chapters' so 
each table will be smaller, and the final document then contains more 
tables - here for example 30 tables consisting of 2 or 3 columns - i.e. 
1 table for 1 chapter.

...And NWP will definitely be as fast as if it only contained 10-20 
pages of pure text.:-)

cheers, Erik Richard

rdavis wrote:
> I'm surprised to hear this. I often have large tables that span multiple
> pages (in page view as well). In fact I'm working on a file right now
> that has a table which spans four pages in page view. No problems.
>
>> Thanks Bob,
>>
>> Sadly it seems that Nisus Pro tables don’t span multiple pages, except
>> in Draft View, and this rather imperfectly, so it’s no great use. Yet,
>> this is something Word or Oppen Office do without any trouble. That’s
>> a feature to be requested —if compatible with .rtf format.
>>
>> On 29.07.2014, at 21.37, Bob Stern <[log in to unmask]
>> <mailto:[log in to unmask]>> wrote:
>>
>>> Nisus's columns definitely will not do what you want.
>>>
>>> Try a table having two columns.  I cannot remember whether there are
>>> problems with a table spanning multiple pages.
>>>
>>> If you need to align related text in the two columns, you need to do
>>> it via table rows.  If not, I believe the entire table can have only
>>> one row.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Erik Richard Sørensen, Member of ADC, <[log in to unmask]>
NisusWriter - The Future In Multilingual Text Processing - www.nisus.com
Openoffice.org - The Modern Productivity Solution - www.openoffice.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~