SPUG: / Spreadsheet::WriteExcel / any experience? /
Jay Scherrer
jay at scherrer.com
Fri Aug 15 23:37:30 CDT 2003
Off the head it looks like your row/columns are getting messed up.
On Friday 15 August 2003 10:29 am, Jim Ludwig wrote:
> Hey again:
> I feed the 6 items of data into a black box, and
> out pops an additional 18 items of data which are
> related to the original 6.
>
> At this point I write out to a different
> spreadsheet with Spreadsheet::WriteExcel -- first
> I write back out the original 6 columns of data,
> and then I write out the other 18 columns of data
> in the same row.
>
> I do this for each row encountered in the original
> spreadsheet from which I'm reading.
>
> ---------------------------------------
> First problem (Spreadsheet::WriteExcel)
> ---------------------------------------
>
> This is where it gets weird, as I'm unable to
> determine where Spreadsheet::WriteExcel is going
> wrong.
>
> gnumeric:
>
> After one spreadsheet was done being processed, I
> tried to open it up using gnumeric, and this was
> the error message I got:
>
> Inconsistent block allocation table
>
And your getting an error because the row/columns are not aligned.
Remember Excel is only a csv file system. Much like your key/value in a hash.
When coverting into an Excel data form why not just use DBD::csv.
> Excel:
>
> I tried opening the same spreadsheet with Excel,
> in a Windows environment, and this was the error
> message I got:
>
> 'foo.xls' cannot be accessed. The file may be
> read-only, or you may be trying to access a
> read-only location. Or, the server the
> document is stored on may not be responding
>
Is the fil locked? Or are you setting permissions acurately?
> ---------------------------------------------
> Second problem (Spreadsheet::WriteExcel::Big)
> ---------------------------------------------
>
> Given the problems I was having with
> Spreadsheet::WriteExcel, I thought it couldn't
> hurt to try Spreadsheet::WriteExcel::Big.
>
> I re-ran my script, and this time the error
> messages were a little different.
>
> gnumeric:
>
> When I opened my resulting file on the command
> line (gnumeric foo.xls), I got this (line wraps
> are mine):
>
> foo.xls
> Excel 95
>
> (gnumeric:24066): gnumeric:read-WARNING **:
> XL: Xf index 0xF00 is not in the
> range[0..0x1E)
>
> ** (gnumeric:24066): CRITICAL **: file
> ../../../plugins/excel/ms-biff.c: line 316
> (ms_biff_query_next): assertion `q->length <
> 20000' failed
> Error, hit end without EOF
>
> ** (gnumeric:24066): CRITICAL **: file
> ../../../plugins/excel/ms-biff.c: line 316
> (ms_biff_query_next): assertion `q->length <
> 20000' failed
>
Is your dtd or data dictionary for the given inputs matching the cell?
Good luck,
Jay
> jim
> _____________________________________________________________
> Seattle Perl Users Group Mailing List
> POST TO: spug-list at mail.pm.org http://spugwiki.perlocity.org
> ACCOUNT CONFIG: http://mail.pm.org/mailman/listinfo/spug-list
> MEETINGS: 3rd Tuesdays, U-District, Seattle WA
> WEB PAGE: http://www.seattleperl.org
--
Personalized e-mail and domain names:
<http://netidentity.com/BI3CCYFM
More information about the spug-list
mailing list