<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Cannot open an excel workbook, "maximum number of columns per sheet" only in 64bit Calc on Windows 10" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116274#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Cannot open an excel workbook, "maximum number of columns per sheet" only in 64bit Calc on Windows 10" href="https://bugs.documentfoundation.org/show_bug.cgi?id=116274">bug 116274</a> from <a class="email" href="mailto:erack@redhat.com" title="Eike Rathke <erack@redhat.com>"> Eike Rathke</a> <pre>Just stating: The .xlsx contains <dimension ref="A1:D37"/> in which area the actual data resides, but also <cols> <col min="1" max="1" width="29.125" style="1" customWidth="1"/> <col min="2" max="2" width="25.125" style="13" customWidth="1"/> <col min="3" max="3" width="32.75" style="5" bestFit="1" customWidth="1"/> <col min="4" max="4" width="31.75" style="2"/> <col min="5" max="16384" width="31.75" style="3"/> </cols> i.e. the grey area right to the data area is covered by min="5" max="16384", probably due to which the overflow dialog is shown. It looks like we should explicitly ignore those column definitions in overflow detection unless cell content data is placed there as well. This "more columns declared than available" may or may not be related to the crash reported here (which I can not reproduce with any version on Linux), just to mention.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>