I do a fair amount of work with Win32::OLE and it's always a good idea to check errors after certain operations. Otherwise, debugging can be quite painful down the road, or if one OLE call dies and snowballs. I use an OLE error checking sub like so: 
$obj=Win32::OLE->GetObject("IIS://localhost/W3SVC/1");
&OLEErrChk("Binding to W3SVC1",1)

[download]
That way you can also trap common errors and act on them, also. 
sub OLEErrChk {
  my $operation=shift;
  my $critical=shift;
  my $errnum=Win32::OLE->LastError;

  if(!$errnum) {
    if ($errnum=~/0x80070094/) {
      print "$operation Failed (in use) trying something..\n";
      &Something;
    }
    else {
      print "$operation Failed: $errnum\n"; 
      die if ($critical);
    }
  }
  else {print "$operation was Successful.\n"}
}

[download]
Hope that helps, Vlad

In reply to Re: Win32::OLE and Excel by vladdrak
in thread Win32::OLE and Excel by nop

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.