Page 1 of 1

Unknown Element "xdr: col" exception

Posted: Wed Oct 16, 2013 1:08 pm
by d3nton
I got an error: 'Unknown Element "xdr: col" exception' when reading this xlsx file:
http://www.file-upload.net/download-818 ... t.zip.html

It seems that XLSReadWrite cannot read <xdr:oneCellAnchor> elements: see xml tag in xl\drawing\drawing1.xml.

Code: Select all

begin
  ExcelFile5 := TXLSReadWriteII5.Create(nil);
  ExcelFile5.Filename := 'C:\test.xlsx';
  ExcelFile5.Read;
end.
Could you please fix this.
Thank you .

Re: Unknown Element "xdr: col" exception

Posted: Thu Oct 17, 2013 3:45 pm
by larsa
Hello

Fixed in update 5.20.05

Re: Unknown Element "xdr: col" exception

Posted: Mon Oct 21, 2013 7:58 am
by d3nton
Hello.

Unfortunately it is not yet fixed in update 5.20.05. Now, I got an EIntOverflow in xpgPXML.pas
function TXpgReadXML.QNameHashB: longword; in the while loops:
->a := a * 378551;

Thanks for your help.

Re: Unknown Element "xdr: col" exception

Posted: Mon Oct 21, 2013 8:32 am
by larsa
Hello

You have turned on overflow checking. Please turn that off.

Re: Unknown Element "xdr: col" exception

Posted: Tue Sep 02, 2014 9:51 am
by kooths
I am using Version 5.20.30, but still get the error

Row 0: Unknown Element "xdr:col"

when trying to open the Excel2007-file zipped into this file:

http://www.diwax.de/testfile.zip

The same happens with similar files containing graphs (the "xdr:col" tag is in the drawing1.xml, drawing2.xml, and drawing3.xml files of the excel file structure). When using the Excel97 version of this file (saved under Excel) and opening it with XLSReadWrite5 everything is fine. But then saving it with XLSReadWrite5 as an Excel2007 file removes the charts and more or less corrupts the file.

By the way, we did not face these problems with exactly the same excel files when working still with XLSReadWrite4.

Help is strongly appreciated.

Thanks in advance and greetings from Berlin

Stefan Kooths

Re: Unknown Element "xdr: col" exception

Posted: Wed Sep 03, 2014 7:02 am
by larsa
Hello

This is fixed (again) in update 5.20.32