Awesome!
Height, Jason wrote:
Andy,
I have almost finished implementing INDEX & DBCell records. The patch that I
attached to the bug report is not 100% correct, however even with it not
being 100% correct there are some test cases that I have where the INDEX &
DBCell records are written correctly and the excel file still doesn't import
into access, so I assumed the problem was with the EXTSSTRecord since this
was the only record that looked "different" in the results from the
BiffViewer.
Give me 24 hours and I should have another patch that is 100% correct for
DBCell and index records.
Jason
-----Original Message-----
From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 4 February 2003 13:39
To: POI Developers List
Subject: Re: ExtSSTRecord [Scanned For Viruses] [Scanned For Viruses]
I think its the INDEX->DBCell + this most likely. We really need to get
to writing those.
Height, Jason wrote:
Andy,
Ok I think that I am well on the way to "fixing it".
There was a bug in the EXTSSTRecord.fillFields so no Info sub records were
being created (so they weren't being displayed in the BiffViewer, and
therefore I couldn't understand how the hell it was working).
The Excel Developers book indicates that it is required when an excel file
has LabelSST and SST records.
This might be contributing to my import in to Access current problems, so
that's why I am investigating it.
Jason
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 4 February 2003 10:27
To: POI Developers List
Subject: Re: ExtSSTRecord [Scanned For Viruses]
This record is for "optimization". It doesn't appear to be necessary and
its completely undocumented (or the documentation is incomprehensible).
OpenOffice doesn't seem to make this record either.
-Andy
----- Original Message -----
From: "Height, Jason" <[EMAIL PROTECTED]>
To: "'POI Mailing List'" <[EMAIL PROTECTED]>
Sent: Monday, February 03, 2003 5:05 PM
Subject: ExtSSTRecord
Hi everyone,
What is the deal with the ExtSSTRecord? There are a few oddities with the
implementation that either I don't understand or are wrong....
Here is the getRecordSize method:
public int getRecordSize()
{
return 6 + 0x3fa - 2;
}
What is that magic 0x3fa number? Shouldn't it be:
public int getRecordSize()
{
return 6 + 8*getNumInfoRecords();
}
A similar issue with the serialise method with also contains that magic
number (0x3fa) ???
I will change it to be what I think is right (as depicted above) unless
someone has an objection or my understanding is not correct.
Please let me know..
Jason
--------------------------------------------------------------------------
------------------------------------------
This e-mail (including attachments) is confidential information of
Australian Submarine Corporation Pty Limited (ASC). It may also be
legally
privileged. Unauthorised use and disclosure is prohibited. ASC is not
taken to have waived confidentiality or privilege if this e-mail was sent
to
you in error. If you have received it in error, please notify the sender
promptly. While ASC takes steps to identify and eliminate viruses, it
cannot confirm that this e-mail is free from them. You should scan this
e-mail for viruses before it is used. The statements in this e-mail are
those of the sender only, unless specifically stated to be those of ASC by
someone with authority to do so.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------------------
----------------------------------------
This e-mail (including attachments) is confidential information of
Australian Submarine Corporation Pty Limited (ASC). It may also be legally
privileged. Unauthorised use and disclosure is prohibited. ASC is not
taken to have waived confidentiality or privilege if this e-mail was sent to
you in error. If you have received it in error, please notify the sender
promptly. While ASC takes steps to identify and eliminate viruses, it
cannot confirm that this e-mail is free from them. You should scan this
e-mail for viruses before it is used. The statements in this e-mail are
those of the sender only, unless specifically stated to be those of ASC by
someone with authority to do so.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------------------------------------------------------
This e-mail (including attachments) is confidential information of Australian Submarine Corporation Pty Limited (ASC). It may also be legally privileged. Unauthorised use and disclosure is prohibited. ASC is not taken to have waived confidentiality or privilege if this e-mail was sent to you in error. If you have received it in error, please notify the sender promptly. While ASC takes steps to identify and eliminate viruses, it cannot confirm that this e-mail is free from them. You should scan this e-mail for viruses before it is used. The statements in this e-mail are those of the sender only, unless specifically stated to be those of ASC by someone with authority to do so.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
