OLE transfer is an old dog, and that's giving MS-resident canines a bad name. :) Think about what it's doing... your program and Excel both reside in main memory, along with the workbook you're creating. Your program talks to the OLE DLLs, which talk to Excel. Excel interprets the command, modifying the workbook. On and on we go, almost certainly causing a few virtual memory swaps long the way.

Spreadsheet::WriteExcel (or WriteExcel::Big) can be your good and loyal friend, giving MS dogs a chance at redemption. S::WE has a much simpler feature set, geared only towards writing content to .XLS files. Much more direct, and much less memory footprint.

Don Wilde
"There's more than one level to any answer."

In reply to Re: Slow Excel access via Win32::OLE by samizdat
in thread Slow Excel access via Win32::OLE by josephjohn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.