_It seems this only applies to OpenXML 2.5. However, v2.5 is shipping with Microsoft products which is super seeds OpenXML 2.0. For future compatibility it would be good to be resolved_
Seems having only a single header row and creating a table in ClosedXML results in a corrupt workbook when opened with Excel 2013.
Excel 2013 handles this in the following ways when creating a new table with only one row of data;
* automatically create a header/data row (Depending on options selected in dialog) to ensure there is more than one row.
* when attempting to delete all rows, a single "empty" data row is retained to comply with the "must have a data row" rule
Comments: ** Comment from web user: jpsfs **
Seems having only a single header row and creating a table in ClosedXML results in a corrupt workbook when opened with Excel 2013.
Excel 2013 handles this in the following ways when creating a new table with only one row of data;
* automatically create a header/data row (Depending on options selected in dialog) to ensure there is more than one row.
* when attempting to delete all rows, a single "empty" data row is retained to comply with the "must have a data row" rule
Comments: ** Comment from web user: jpsfs **
I can reproduce this also.
The workaround at this moment is:
> Insert a empty row in the table;
> Save the workbook;
> Delete the empty row;
> Save the workbook again.
This generates a lot of IO operations, undermining the performance.