--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > Sorry to here ill. Get well soon.
Thanks, its been a rough few days but I do feel better today. I played with set_arg_types a bit and liked it. Using it persistent before looping that Search method in the InDesign script allows the InDesign Search function (using dot syntax) to work fine with ANSI arguments (including where some vector values happen to be digits that need to be sent as string to VARIANT in-arguments). I think the most objectionable thing about getting com exceptions is that there is generally no clue of what's gone wrong. If I deliberately send a number to the VARIANT argument using vbscript I get an error message from InDesign: --------------------------- Windows Script Host --------------------------- Script: C:\Documents and Settings\Sheri\My Documents\TestCC206\PowerProData\scripts\TestIndesign.vbs Line: 11 Char: 1 Error: Invalid value for parameter 'For' of event 'Search'. Expected String, but received 123. Code: 800A770D Source: C:\Program Files\Adobe\Adobe InDesign CS2\InDesign.exe --------------------------- OK --------------------------- I've noticed other erroneous things gracefully handled in vbscript that done with PP/com script either crash Powerpro or give exceptions. Some research reveals suggests the possibility to query for an error object when invokes return. Have a look at IErrorInfo both at msdn and <http://www.devguy.com/fp/Tips/COM/> and see if of any value. > > I found what might have caused a false error message in previous > version. Will compile change when I get home next week (snow > permitting). We had uncommonly much deep snow here in December. Another light dusting this week. I guess it remains to be seen if the addition VT_VARIANT|VT_BYREF will be useful or not. Regards, Sheri
