| Package home | Report new bug | New search | Development Roadmap | Status: Open | Feedback | All | Closed Since Version 0.9.4 |
| Bug #14281 | Using a row > 16,384 reports error | ||
|---|---|---|---|
| Submitted: | 2008-07-02 15:36 UTC | ||
| From: | edspain | Assigned: | cschmitz |
| Status: | Closed | Package: | Spreadsheet_Excel_Writer (version 0.9.2) |
| PHP Version: | All | OS: | All |
| Roadmaps: | (Not assigned) | ||
[2008-07-02 15:36 UTC] edspain
(Ed Eichman)
Description:
------------
If I use a row > 16,384 in a formula, I get the error "Row in: xxx greater than 16384", even when I use setVersion(8). John McNamara said back in 2002 that this would be fixed in the next version (http://www.dbforums.com/showthread.php?t=356247), but apparently this is not even reported as a bug. I report it hear for completeness.
Test script:
---------------
<?php
require_once('Spreadsheet/Excel/Writer.php');
$workbook = new Spreadsheet_Excel_Writer();
$workbook->setVersion(8); //same bug also happens w/o setVersion
$workbook->send('Sales.xls');
$worksheet =& $workbook->addWorksheet('Sales');
$worksheet->write(0, 0, "5");
$worksheet->write(16385, 0, "10");
$worksheet->writeFormula(16386, 0, "=SUM(A1:A16385)");
//hide unnecessary rows so that the error can be seen.
for ($jj = 1; $jj<=16384; $jj++)
$worksheet->setRow ($jj, null, 0, true);
$workbook->close();
?>
Expected result:
----------------
Cell A16387 should show 15, with formula "SUM(A1:A16385)"
Actual result:
--------------
Cell A16387 shows text "Row in: A16385 greater than 16384"
Comments
[2008-07-05 00:28 UTC] dufuz
(Helgi Þormar Þorbjörnsson)
Do note that the forum post you are talking about is about the CPAN excel writer module, which is Perl, not PHP.
[2009-11-29 06:15 UTC] cschmitz
(Carsten Schmitz)
-Status: Open
+Status: Assigned
-Package Version: 0.9.1
+Package Version: 0.9.2
-Assigned To:
+Assigned To: cschmitz
[2009-11-29 06:23 UTC] cschmitz
(Carsten Schmitz)
-Status: Assigned
+Status: Closed
This bug has been fixed in SVN.
If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET).
If this was a problem with the pear.php.net website, the change should be live shortly.
Otherwise, the fix will appear in the package's next release.
Thank you for the report and for helping us make PEAR better.