--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote:
> Yeah, that makes sense. Remember, I do two passes. You see error > message for second pass. Pass I: Guess. Pass II: send everything > in as strings (logical order: I keep track of whether any > parameter was converted by guess in pass one: if no such > conversion made, no point in Pass II). If you don't even know which, or even if, its an argument type that is in error, making multiple passes makes no sense to me. Now that you are getting errors that the user can act on, I think it would be best if you did the same. Maybe we should try a no-guess model again. I believe you are calling functions that will try to coerce what is needed from the VARIANTs received. But for whatever reason, sometimes the called functions can't do that. Maybe it can't do it if you send it a specific type in the variant. Maybe it needs a VT_VARIANT and VT_VARIANT can only be sent as VT_BYREF. Presumedly the pointer can point to a Variant of a specific type such as VT_BSTR. The other possibility it has something to do with which process the Variant data lives in. Either way, using VT_VARIANT|VT_BYREF could be the answer. > > I think you did local r=myselect.Search(chgVec[i,1], wholeword, > casesensitive, chgVec[i,2]) equivalent in vbs and it worked? I can't really model Powerpro's regex to 2d vector into vbscript. Vbscript, if passed 123 instead of "123" for parameter #1 of the Search method gives an Indesign error message for Parameter #1. You could now do the same. Regards, Sheri
