Why is range.CreateTable("myTable") with 0 rows not possible? #2649
Replies: 1 comment
-
Because Excel doesn't allow 0 row tables. The reason is likely same as for why ClosedXML doesn't allow it. Allowing 0 row makes life miserable, because once there is no header and no total and there is 0 rows, there is no valid reference to the table area - that is invalid. 1:1 conversion between structure reference and A1/R1C1 notation wouldn't work (empty data area can't be turned into a valid reference). That would cause problems with total calculations and many other similar things. I don't know (nor really care) how can EPPlus can create 0 row, but when I try, Excel reports problem with content.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We'd like to use ClosedXml to replace EPPlus.
One issue we have, is, that we'd like to create tables with 0 rows, but we get the error "Table 'myTable' should have at least 1 row".
In my opinion it should be possible to create tables with 0 rows. It is possible in EPPlus and also in all databases (which an excel-file is kind of).
Is there a workaround for this?
Is there a specific reason, why it is not possible?
Thank you for your support!
Beta Was this translation helpful? Give feedback.
All reactions