<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2> I ran this in the debugger, and the
return value is actually a VT_BOOL (true), which</FONT></DIV>
<DIV><FONT face=Arial size=2>equates to 1. Since the return type at the
C++ level is different from what the typelib</FONT></DIV>
<DIV><FONT face=Arial size=2>specifies, I'd guess this is either bad type info
in the typelib or a bug in the Excel api itself.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2> Oddly enough, it
succeeded after I ran makepy for the excel typelib
However, only</FONT></DIV>
<DIV><FONT face=Arial size=2>because it wraps the returned bool in the Series
generated class.</FONT></DIV>
<DIV><FONT face=Arial size=2>The returned object is unusable, but at least it
doesn't blow up.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2> It looks like there's a potential
bug in the dynamic dispatch code, though. InvokeTypes</FONT></DIV>
<DIV><FONT face=Arial size=2>can return </FONT><FONT face=Arial size=2>a tuple
if there are any out parameters to be returned, but there's a slight
</FONT></DIV>
<DIV><FONT face=Arial size=2>difference between the way the python code checks
for out parameters (in build.py) </FONT></DIV>
<DIV><FONT face=Arial size=2>and the way the C++ </FONT><FONT face=Arial
size=2>code determines it
(PythonOleArgHelper::ParseTypeInformation).</FONT></DIV>
<DIV><FONT face=Arial size=2>If the two come up with different interpretations
of the number of out params, </FONT><FONT face=Arial size=2>you
could</FONT></DIV>
<DIV><FONT face=Arial size=2>end up doing a Dispatch of a tuple.</FONT></DIV>
<DIV><FONT face=Arial
size=2> hth</FONT></DIV>
<DIV><FONT face=Arial
size=2>
Roger</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>