From: Chuck Remes <cremes.devlist@...>
Date: 2010-04-08T20:29:43+09:00
Subject: Re: Complicated output parameter in WIN32OLE

On Apr 7, 2010, at 11:33 PM, Mitchell Hashimoto wrote:

> Chuck Remes wrote:
>> I'm not sure what to do here either. Have you tried retrieving the 
>> WIN32OLE_METHOD and then looping through each param and asking its 
>> #ole_type?
>> 
>> Check out WIN32OLE_PARAM.ole_type for the general idea.
> 
> Chuck,
> 
> Thanks for the response. I looped through each to print out the ole_type 
> and got the following:
> 
> VirtualSystemDescription,VirtualSystemDescription
> BSTR,BSTR
> BSTR,BSTR
> BSTR,BSTR
> 
> I'm not sure why there are two for each? Besides that, do these types 
> mean something useful for the refs (for arrays)?

I don't really know how to deal with the VirtualSystemDescription but at least we know the BSTR maps to VT_BSTR in WIN32OLE::VARIANT. That's a good start. 

So for BSTR use WIN32OLE::VARIANT::BSTR and for VirtualSystemDescription try WIN32OLE::VARIANT::VT_VARIANT. See what happens when you invoke the method with that argument list.

cr