--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote:
> > Let't just test that. comPlugin0.72_091218_no_guesses.zip in the > usual place is exactly the same as comPlugin0.72_091217.zip, > except in cases where arguments types are not known > (VT_VARIANTs), it does _not_ attempt to guess type based on > string contents, but leaves as a VT_BSTR. That may break other > calls to other methods, but for now, does that fix your > myselect.Search calls? Interesting. using comPlugin0.72_091218_no_guesses I get (for the values in the first row of the vector): local r=myselect.Search(chgVec[i,1], wholeword, casesensitive, chgVec[i,2]) ERROR: com.method: Invoke failed (sys code 80020009: "Exception occurred.") If I click "OK", I get a series of errors because I reference r and r is invalid (since above iteration had a com exception). If I click "OK" on all of those, the subsequent rows and values do work. So it isn't because of the booleans getting mistyped in the subsequent usages (the booleans are also "Variant" in the typelibrary). So there is evidently still a problem strictly related to the vector value that is is all digits. If I use unicode.new on the vector values, it still works for all the iterations without error. Maybe you should make a version that prints out to file what vt it is actually setting. >From my reasearch VT_VARIANT for a VARIANTARG is not valid. It must be >VT_VARIANT|VT_BYREF pointing to another variable which is VT_VARIANT. Not that >I strictly understand what all that means. I read that those settings are >available for "languages that allow the variant type to be changed". Regards, Sheri
