No, no Page Setups. And I'm using C#.
I've narrowed it down to the problem being due to the number of merged
cells, also affected by how deep into the sheet (the largeness of the
row number) they are.
Each page contains a matrix of 20 "virtual rows" (each made up of 3
Excel rows) by 8 "virtual columns" (each column being made up of around
8 Excel columns).
Each virtual cell has either one merged cell (3 rows by 8 columns) or 2
merged cells (either 1 row or 2 rows by 8 columns).
As I mentioned, if there is only one page per Worksheet, I don't run
into this problem, though there is an aggregate same number of merged
cells.
I have a sneaky feeling it has something to do with memory management
that requires a huge amount of memory within a Worksheet that is avoided
if the same data is stored in separate Worksheets.
Joe
*** Sent via Developersdex
http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!