in reply to OLE module working 'part-time'

Aim9b:

You might consider using Spreadsheet::WriteExcel, unless you're using Excel features that it doesn't handle yet. It's quite simple to use, and you avoid having hung Excel processes running in the background. (Been there, done that.)

...roboticus

Replies are listed 'Best First'.
Re^2: OLE module working 'part-time'
by Aim9b (Monk) on Sep 25, 2007 at 10:48 UTC
    Thanks, I think that's how I started out, then I ran across the OLE sample. I have no idea which approach is better. At one time, I thought that I read where one included the other. I'm still learning & the curve seems to be getting steeper as I go.

    This is a typical user, so I have no idea how the spreadsheet will evolve. Right now, we're at the "all I need is" stage. But we know how long THAT will last. Currently I just need to generate a sheet per day, one for the week, & a summary page. But as for other features, only time will tell. I'll go back & see what I have from my early version. Thanks again.
[reply]
      I had to use the Spreadsheet module because we don't have office products on our servers, yet the users still wanted their spreadsheets. For a while, we used .CSV files which made our merchant IDs hideous (they're 16 digit numbers, which Excel helpfully reformatted into reals...). Then I stumbled across this package and never looked back.

      ...roboticus

[reply]
        That WOULD be a limitation, for sure. If we have MS Office on all the boxes, would you prefer one method over the other. Also, I'm leaning towards using Text::CSV, do you have any insight to that vs. Text::CSV_XS, Text::xSV, etc.? Thanks.
[reply]

In Section Seekers of Perl Wisdom