Maximum number of columns exceeded warning

Hi,

I use the LibraOffice on windows 10 and see this error.

“The data could not be loaded completely because the maximum number of columns per sheet was exceeded” Warning

Please help on the same.

Thanks,
Bujji

The problem persists is Version: 6.3.1.2 Build ID: 1:6.3.1~rc2-0ubuntu0.18.04.1~lo1 (Linux). I doubt I am missing any actual data since none of the sheets at more than arond 25 columns of data (there are a lot of sheets). Obviously the problem remains unaddressed despite numerous claims versions much earlier than this would address it.

Despite the fact I dio not think I am missing data, doubt is left. Another obstacle to open widespread open source adoption.

Yup - same problem here

I am using LibreOffice Calc version 6.3.4.2, my workbook (xlsx) has three sheets. (Sheet 1: 6 columns , 10000 rows.) (Sheet 2: 6 columns, 202 rows) (Sheet 3: 11 columns , 212 rows) -----> This problem still exists.

Version: 6.4.3.2 (x64) opens all rows, and are USERS of MS Excel spreadsheets utilizing more columns beyond what is provided in LibreOffice Calc? LibreOffice appears to have 338 columns.

Calc limits

Ongoing work to increase column count

Likely not related (unless there are really more than 1024 columns used), see my answer.

I am using LibreOffice Calc version 6.3.4.2, my workbook (xlsx) has three sheets. (Sheet 1: 6 columns , 10000 rows.) (Sheet 2: 6 columns, 202 rows) (Sheet 3: 11 columns , 212 rows) -----> This problem still exists.

What are the actual experiences with sheets of more than 1024 cells in software allowing for that?
What should be expected if the maximum number one day will be 2048?
Someone will want 2050 columns, I suppose.
Did everybody consider how to address the 10000th column?
Well, let’s make “square” sheets with (as it currently is) 2^20 (=1048576) rows and the same number of columns. Of course, everybody here knows that the (still existing!) last column will be addressed by BGQCV. And 100 columns left of it?
Considering higher numbers of columns should include a new syntax for true absolute and relative addressing based on ordinary numbers. That is, in fact, the way references in tokenized formulas are represented.
The RC addressing anyway was much more logical and only suffered from its unhandiness in the relative case. Let’s introduce a more handy way then instead of trying to digest all that letter salad forever.

tdf#116274 and tdf#116939 will be fixed in 6.0.4 (and btw it’s always good to state the version number you use).

I agree to be clear we need to provide the version. I’m using latest 6.0.3 version. I will wait for the latest release 6.0.4. Is there some tentative time for the new release?

Released today.

I just installed 6.0.4.2 (x64) on a Windows 10 machine. Yet this problem persists. Any update? Thanks in advance.

Your document probably has applied custom widths to columns >1024, see tdf#116939#c22. It’s not a real problem, just a warning, albeit confusing, hence that check will be disabled for 6.0.5.

Same error. Version 6.0.5.2.

The file in question has 22 worksheets. There are references to other sheet. But they are at most N columns (14 columns).

So the error actually indicates something else is causing it.

Another xlsx has 17 worksheets. There are at most M columns (13). Got the same error.

Both file open correctly, though.

Upgrade to 6.1.0.3 . Both xlsx are seeing the same errors but still open fine.

Upgraded to 6.1.2 and still getting this warning on multiple xlsx’s, eventhough there’s not where near the 1024 column limit. Will this ever be fixed?

Where’s your document and how can you be sure that Excel doesn’t write something that tells that a column > 1024 is used? If it’s about one of the documents mentioned in tdf#116274 then see https://bugs.documentfoundation.org/show_bug.cgi?id=116274#c46 for why the warning is correct.

1 Like

I am using LibreOffice Calc version 6.3.4.2, my workbook (xlsx) has three sheets. (Sheet 1: 6 columns , 10000 rows.) (Sheet 2: 6 columns, 202 rows) (Sheet 3: 11 columns , 212 rows) -----> This problem still exists.