--- Mark Hammond <[EMAIL PROTECTED]> wrote: > At this stage the problem is more confusion as to > exactly what is happening. > My understanding is: > > * Their type-library defines that method as having a > variant type of > VT_LPSTR. > * Microsoft declares in wtypes.h that VT_LPSTR is > valid in a typedesc, but > *not* in a VARIANT. > * When Python processes the typelib, it makes no > attempt to translate > VT_LPSTR to a type that is valid in a Variant. > * When Python is making the call to the COM object, > it sees that VT_LPSTR - > but as it is filling a VARIANT, it gives that error > (the error could be > clearer - but that is the underlying reason for that > type not being > supported)
Yup. The analysis above seems correct given the information we have. > > The last experiment I asked you to perform should > have translated the > VT_LPSTR from the typelib into a VT_BSTR - the > "standard" string type - but > that still failed. You may also like to change the > 30 to 12 (VT_VARIANT) > and see if that helps. But ultimately, I need to > know exactly what variant > type the COM object is expecting, and why it fails > if a VT_BSTR variant is > supplied. I tried changing 30 to 12. Didn't work. The com object gave "Bad argument type" error as with 8. It seems like a problem with the COM object. I am going to ask the object authors about the exact type the object expects as argument. That will hopefully shed some light on what's happening. Thanks! -Sumeet. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
