--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > OK, try this then. Create the VARIANT with VT_ERROR etc. Send a > > pointer to this VARIANT using VT_VARIANT|VT_BYREF. Its the only > > way to ensure that another process is going to see this VARIANT > > exactly the way you make it. > > comPlugin0.72_100118.zip. I did that thing, but didn't test, > except that it seems a "t" though in at least one case: excel > getfilewSaveAs I think it was.
Oh well. Skipping the dictionary parameter for XLApp.CheckSpelling still uses and sets the dictionary to empty string instead of using and retaining the previously existing default. (too bad). > > Finally figured out how to get at least some extra error info > with IDispatch::Invoke fails. objApp.Help(4) in word now gives > mch same error as vbs. Great! Tried it saw that, then tried in my InDesign Search test. Very interesting result! The error reported is not for the digits instead of string on Parameter #1 (For), but for string "0" instead of digit/boolean 0 on Parameter #2 (WholeWord). But I only get the error where chgVec[i,1] (Parameter #1) is digits instead of string. The other invokes don't mind the value they are receiving for Parameter #2 (which is unchanged; however I suppose the guesser is sending zero, not "0" for those occurrences). Error 770d: C:\Program Files\Adobe\Adobe InDesign CS2\InDesign.exe: Invalid value for parameter 'WholeWord' of event 'Search'. Expected Boolean, but received "0". local r=myselect.Search(chgVec[i,1], wholeword, casesensitive, chgVec[i,2]) All the Search method's in parameters are Optional VARIANTs.
