Hrm.. I can run this just fine on my W2k box (only changed the path's). Make sure that your path etc is correct, print out what you are adding to the array prior to pushing it in there.
Also, perhaps just a style thing, but I think that
foreach $elem (@allfiles){ if ($elem =~ /[\d\w\s]+\.$filename/){ #rest of if code }
looks much nicer and is much easer to read than those for loops, or even better drop the $elem alltogether and use $_.

Update: If I change the "\\" to "/" (forward slashes should work the same as double-backslashes) I now get the error, otherwise everything still works fine...

In reply to Re: Using Win32::OLE 'Excel' and stumped by the_slycer
in thread Using Win32::OLE 'Excel' and stumped by cacharbe

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.