Broken XLSX file due to CustomXML

[d3nton]

Hello!

I currently try to help a user of our application to fix a problem regarding a broken xlsx file.
Unfortunately I cannot send the xlsx file due to privacy reasons.
Excel reports that the file was broken but it can be repaired. I extracted both files (original and repaired) and compared them.
The difference is a customXML folder which has been created in the original file. The repaired file does not contain this folder and all references to this folder has been deleted
by Excel in order to repair the file and the result seems to be correct.
My question: In which case does XLSReadwrite create such a customXML folder? Maybe this helps me to find a solution for the problem.

[larsa]

Hello

I need an Excel file which contains the customXML folder in order to take a look at this.

[d3nton]

Okay. I have sent you a PM.

[larsa]

Hello

Excel reports that the file is damaged. Please send me a file that can be opened in Excel without error.

[d3nton]

Yes, that's exactly the issue which I described above.
The file has been created as damaged file with XLSXReadWrite.
You can repair it with Excel (what I did) in order to take a look at the differences between the "original" file which has been created with XLSREadWrite
and the file which has been saved after repairing it with Excel.
The only bigger difference was the "CustomXML" folder which is only present in the damaged file (if you extract the xlsx file with e.g. 7zip).
I opened this ticket since I am not sure, why exactly XLSReadWrite creates such a CustomXML folder and damage the file and how to fix it.
I have sent you a link to the repaired Excel file.

[larsa]

Hello

Have you created the file from scratch with XLSReadWiteII? This is not possible, you must have loaded a template before as the component never writes the customXml folder.

[d3nton]

Okay, thanks. I will check this.