This is a caveat about passing/returning arrays to VBScript from an "external" source. This was alluded to in my
July 29 post on microsoft.public.scripting.vbscript entitled Returning arrays from a .vbs file. Unfortunately, the
situation seems worse than I originally thought. In that post I gave an example of invoking a VBScript file from
another one and using IE to pass back a result array. Unfortnately, this array seems to get corrupted, at least in
the arrangement that I have. It think even simple numeric values can sometimes not be passed back. The thing that
makes it really bad is that it seems to happen semirandomely.
The summary is that when I return an array from my OCX to the calling VBScript file, it is *sometimes* (but
consistently) corrupted. It especially likes to happen when I return arrays of IE DOM elements.
The fix that works for me is to put all the items from the array into a dictionary as keys (implies an array of
unique elements) and then return theDictionary.Keys array. Still, this is not good behaviour.
Hope this helps someone,
Csaba Gabor from New York