Skip Menu |

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

Maintainer(s)' notes

If you are reporting a bug in Spreadsheet::WriteExcel 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::WriteExcel
                      Parse::RecDescent
                      File::Temp
                      OLE::Storage_Lite
                      IO::Stringy
                      Spreadsheet::ParseExcel
                      Scalar::Util
                      Unicode::Map
                    );

    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::WriteExcel (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 but complete example program that demonstrates your problem. The program should be as small as possible. At the same time it should be a complete program that generates an Excel file. If the Spreadsheet::WriteExcel section is part of a much larger program then simplify it down to the essentials. Simulate any DB reads with an array.

5) Say if you tested with Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.

6) If you are submitting a patch you should check with the author 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::WriteExcel Google Group.

Report information
The Basics
Id: 37991
Status: resolved
Priority: 0/
Queue: Spreadsheet-WriteExcel

People
Owner: Nobody in particular
Requestors: arkaig1 [...] yahoo.com
Cc:
AdminCc:

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



Subject: Workbook::close returns false if > 7MB and filehandle passed to new()
Date: Mon, 28 Jul 2008 06:59:24 -0700 (PDT)
To: bug-Spreadsheet-WriteExcel [...] rt.cpan.org
From: Barry Gates <arkaig1 [...] yahoo.com>
$obj->close() drops out, returning $obj->{_internal_fh} (0), as its last interpretted expression, when $obj->{_biffsize} > 7 MB, and $obj->{_internal_fh} is not set.  That is, OLE::Storage_Lite is needed, and when a file handle and not a file name was passed to Spreadsheet::WriteExcel::new.   By the way, on return, $! was set to Errno::EBADF (9, Bad file descriptor), under my circumstances anyway.  This caused some head-scratching, and initial debugging misdirection.  It's perfectly ok by me (at this time) if this it not worth trying to avoid.  Lastly, examples/bigfiles.pl might be quicker to understand, as not containing anything particularly "exemplary", other than its own largesse (of course), if its comments explicitly mentioned that no special subroutine calls or require-statements were needed to get the support of big files by this module. This is a very neat package, though. Many thanks! Barry Gates dist: Spreadsheet-WriteExcel-2.18 (all seem to still remain as noted in 2.22) perl: 5.8.5 o.s.: GNU/Linux #1 ... text: Write Excel .XLS biff size my $maxsize 7_340_032 7MB - 247KB 7_087_104
On Mon Jul 28 09:59:58 2008, arkaig1@yahoo.com wrote: Show quoted text
> $obj->close() drops out, returning $obj->{_internal_fh} (0), as its > last interpretted expression, when $obj->{_biffsize} > 7 MB, and > $obj->{_internal_fh} is not set.  That is, OLE::Storage_Lite is > needed, and when a file handle and not a file name was passed to > Spreadsheet::WriteExcel::new.
Hi Barry, Thanks for that, I'll look into it. Show quoted text
> Lastly, > examples/bigfiles.pl might be quicker to understand, as not > containing anything particularly "exemplary", other than its own > largesse (of course), if its comments explicitly mentioned that no > special subroutine calls or require-statements were needed to get > the support of big files by this module.
Good point. That example evolved from an older version that did need some special handling. However, that is no longer the case so I will update it. Thanks, John. --
Subject: Re: [rt.cpan.org #37991] Workbook::close returns false if > 7MB and filehandle passed to new()
Date: Wed, 30 Jul 2008 10:56:39 -0700 (PDT)
To: bug-Spreadsheet-WriteExcel [...] rt.cpan.org
From: Barry Gates <arkaig1 [...] yahoo.com>
I look forward to the official fix.  I will probably wait for the "other" bug (MSO3SP3) to be fixed before I do a reinstall [I'm somewhat "newbie" in this ballpark.], but I'll take a look when mine is done, either way.  Thanks again! --Barry --- On Mon, 7/28/08, John McNamara via RT <bug-Spreadsheet-WriteExcel@rt.cpan.org> wrote: From: John McNamara via RT <bug-Spreadsheet-WriteExcel@rt.cpan.org> Subject: [rt.cpan.org #37991] Workbook::close returns false if > 7MB and filehandle passed to new() To: arkaig1@yahoo.com Date: Monday, July 28, 2008, 3:02 PM <URL: http://rt.cpan.org/Ticket/Display.html?id=37991 > On Mon Jul 28 09:59:58 2008, arkaig1@yahoo.com wrote: Show quoted text
> $obj->close() drops out, returning $obj->{_internal_fh} (0), as its > last interpretted expression, when $obj->{_biffsize} > 7 MB, and > $obj->{_internal_fh} is not set.  That is, OLE::Storage_Lite is > needed, and when a file handle and not a file name was passed to > Spreadsheet::WriteExcel::new.
Hi Barry, Thanks for that, I'll look into it. Show quoted text
> Lastly, > examples/bigfiles.pl might be quicker to understand, as not > containing anything particularly "exemplary", other than its
own Show quoted text
> largesse (of course), if its comments explicitly mentioned that no > special subroutine calls or require-statements were needed to get > the support of big files by this module.
Good point. That example evolved from an older version that did need some special handling. However, that is no longer the case so I will update it. Thanks, John. --
Closing this issue. Can't fix. Suggest using Excel::Writer::XLSX instead.