> In either case, the documentation is wrong. Unless you need a > non-zero lower > bound, I would just use 0 for it and go on. Otherwise, build a > test case...
I actually found a sample online from someone who had used 1 as the base; so I tried it - but it made no difference. I also tried SafeArrayCreate() at Ehsan's suggestion, with and without filling the array using SafeArrayPutElement()... none of it made any difference. It seems to be something wrong with either the passing mechanism between the two, or perhaps more likely, something odd about VB trying to process the data at the receive end, since the exception occurs in the client but the call stack just shows MSVBM60 (rather unhelpful). I can't believe that all those methods for safearrays could be faulty! Microsoft public newsgroups have given no response... mind you, it's hard to find a group specific to ActiveX interaction with VB. I had to choose the best three groups I could find. -- Jason Teagle [EMAIL PROTECTED]
