Does anyone have experience with Win32::OLE and MSMQ?

I have a script that I want to port from using a database to using MSMQ. The problem is that the MSMQ queue messages are themselves COM objects. I can create the MSMQQueueInfo and MSMQQueue objects fine, and Peek or Receive messages from the queue. The problem is that the MSMQMessage objects that are returned do not return the COM object as the message Body property, but rather a Win32::OLE::Variant of type VT_ERROR. Am I asking too much of the Win32::OLE module?

I have alternatives (rewrite as a WSH JScript, which is ok except I want the script to translate the messages and send as e-mail messages, which would mean CDONTS and running IIS SMTP server on an already overloaded machine, or rewrite as C++ or Delphi, which means a lot more work).

In reply to Win32::OLE and MSMQ by p.dragicevich

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.