Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Spreadsheet-ParseExcel CPAN distribution.

Maintainer(s)' notes

If you are reporting a bug in Spreadsheet::ParseExcel here are some pointers

1) State the issues as clearly and as concisely as possible. A simple program or Excel test file (see below) will often explain the issue better than a lot of text.

2) Provide information on your system, version of perl and module versions. The following program will generate everything that is required. Put this information in your bug report.

    #!/usr/bin/perl -w

    print "\n    Perl version   : $]";
    print "\n    OS name        : $^O";
    print "\n    Module versions: (not all are required)\n";

    my @modules = qw(
                      Spreadsheet::ParseExcel
                      Scalar::Util
                      Unicode::Map
                      Spreadsheet::WriteExcel
                      Parse::RecDescent
                      File::Temp
                      OLE::Storage_Lite
                      IO::Stringy
                    );

    for my $module (@modules) {
        my $version;
        eval "require $module";

        if (not $@) {
            $version = $module->VERSION;
            $version = '(unknown)' if not defined $version;
        }
        else {
            $version = '(not installed)';
        }

        printf "%21s%-24s\t%s\n", "", $module, $version;
    }

    __END__

3) Upgrade to the latest version of Spreadsheet::ParseExcel (or at least test on a system with an upgraded version). The issue you are reporting may already have been fixed.

4) Create a small example program that demonstrates your problem. The program should be as small as possible. A few lines of codes are worth tens of lines of text when trying to describe a bug.

5) Supply an Excel file that demonstrates the problem. This is very important. If the file is big, or contains confidential information, try to reduce it down to the smallest Excel file that represents the issue. If you don't wish to post a file here then send it to me directly: jmcnamara@cpan.org

6) Say if the test file was created by Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.

7) If you are submitting a patch you should check with the maintainer whether the issue has already been patched or if a fix is in the works. Patches should be accompanied by test cases.

Asking a question

If you would like to ask a more general question there is the Spreadsheet::ParseExcel Google Group.

Report information
The Basics
Id: 13365
Status: resolved
Worked: 4 hours (240 min)
Priority: 0/
Queue: Spreadsheet-ParseExcel

People
Owner: Nobody in particular
Requestors: roels [...] mpi.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.2603
Fixed in: (no value)

Attachments


Subject: mis-parsing worksheet of workbook with graphs of data on second worksheet
OLE/Storage_Lite.pm 0.14 Spreadsheet/ParseExcel.pm 0.2603 perl v5.8.0 sun4-solaris SunOS kobuk 5.8 Generic_117350-21 sun4u sparc I'm having problems parsing certain workbooks. I'm using Excel 2002 SP2 on Win2000. Saving in earlier excel format seems to have no effect. I see the problem when the workbook consists of two worksheets, and the first contains two graphs based on data in the second. Two sheet objects are created with the right names, but the data from the second sheet is in the first object, and the second sheet object is empty. That is, data from the first sheet is lost. Attached you will find the following: a perl test script (basically the code from the docs) a test file that fails (test.xls) three derivative files that parse OK (two where one or the other graph was deleted, and one where the order of the two worksheets was reversed) a log file with the script output (including module versions) an error file showing the structure of the parsed objects
Download test_eval.tar.gz
application/x-gzip 25.1k

Message body not shown because it is not plain text.

Hi, This issue is fixed in version 0.47 of Spreadsheet::WriteExcel. Thanks for your input, John. --