On my browser, this (1) prompts "do you want to open or save this downloaded file?" and (2) opens TWO windows, one blank.

As to why you see two windows, I cannot say. I cannot replicate this behaviour. Maybe someone with more CGI experience could explain this. However, I have noted some small differences in the way Netscape and IE handle the example program. The joys of CGI and browsers, I guess. %^)

If you wish to stream the file to Excel you can set the Content-type as follows:     print "Content-type: application/vnd.ms-excel\n\n"; If you wish to prompt the user to view the file or save it with a specified filename you can do something like the following:

    my $filename ="cgitest.xls";
    print "Content-type: application/vnd.ms-excel\n";
    print "Content-Disposition: attachment; filename=$filename\n\n";
[download]

The example that you posted has been updated in more recent versions of the module to highlight these options. However, the view or save options can be overridden by the client browser.


Can you comment on your tie soln above, and the alternative as per cgi.pl?

In a CGI program you have to redirect the Excel file to STDOUT. The easiest way to do this is to use the "Minus" file as a file name in the constructor:     my $workbook = Spreadsheet::WriteExcel->new("-"); The "Minus" file is documented in perlopentut*. The comment in the above example refers to it as a filehandle but it isn't, it is a file name.

As such you do not need to use tie at all in this situation. You would only need to use the above technique if you wanted to do something unusual such as stream the file to a browser and save a local copy.

The option of passing filehandles to the constructor was introduced mainly to allow the files to be streamed over sockets and to allow Spreadsheet::WriteExcel to work with mod_perl.

John.
--
* Does anyone know of anywhere else that this is documented?

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.