This exception
OLE exception from "Microsoft Office Excel" 'SLOC_Count_C_Sharp_Macro' could not be found. Check the spelling of the file name, and verify the file location is correct tells me that the string
"Personal.xls!SLOC_Count_C_Sharp_Macro" is not meaningful to Win32::OLE, or is simply incorrect.

I'm not sure that win32::ole allows you to run a macro from a workbook that you haven't opened. Have you tried this:

my $macroExcel = Win32::OLE::Strict->new('Excel.Application') or die;
my $macroBook = $macroExcel->Workbooks->open($myPersonalMacros) or die
+;
$macroExcel->run("SLOC_Count_C_Sharp_Macro");

[download]

And please, please, read How do I compose an effective node title?, How do I post a question effectively?, and Markup in the Monastery!

In reply to Re^2: Using Win32::OLE and Excel - Tips and Tricks by jrsimmon
in thread Re: Using Win32::OLE and Excel - Tips and Tricks by Anonymous Monk

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.