To your earlier question: there is no output (except the count output before the loop) since it hits the error.
The VB Script & PDF are part of my history with this. The PDF contains Excel/VBA example, and it works for me too. In fact that is the solution we used and I left this forum for over a month!
The VB Script is from a colleague and it does not work. This triggered an interest in an alternative and I googled and found AutoIt! AutoIt was better than VBScript since gave a Type Mismatch on the call which AutoIt does execute it and return everything, except the first element of the list.
I suspect it is the way arguments are handled in AutoIt specially when using with calls to COM objects. I can get some insight from an expert like you.
My AutoIt script uses this as : $p.GetNameList(7, $list, $count)
$list returns are an array with index 0 to 26 (matches the $count with returns 27). Elements $list to  do contains the proper string values (e.g. 'RB-136H') but element  contains a left pointing arrow (seems to be line feed since when I copied it from the output of ConsoleWrite and pasted it here it takes me to a new line with no visible character).
Another Get method ( for which OLE/COM Object viewer says ):
Are these limitations of AutoIt w.r.t. COM or am I doing something wrong?
Thanks for any insight into this. This will really decide if we adopt AutoIt as our chosen scripting solution of choice. It has given us an extremely good impression otherwise. The functions work fine with Excel/VBA but have problems with VBScript.