Gary,


>if the array is dimensioned with 12 elements (i.e., DIMENSION laFinger[12]), then the size is 12x12 or 144...
>

This is after the ActiveX control is called, correct? That sure looks like the control is re-dimensioning the array.


Not really, Gary. I have DIMENSIONed the array BEFORE I called the ActiveX Export method.

But, the interesting thing is that if I initialized the array (AS Byte) with 12 elements (DIMENSION laFinger[12]), after calling the ActiveX method, it now returns 12 elements still, but each element is filled with 12 bytes of 'gibberish' or what looks like hexadecimal stuff.

If I DIMENSION it with 1024 (DIMENSION laFinger[1024]), then call the Export method, the array still also has 1024 elements, but each element is filled with 1024 bytes as well.


>VFP8 and later can pass byte arrays by_ref to a COM server. Before that, we were out of luck. No matter what was done with COMARRAY, VFP passed by val only. Drove me crazy about 10 years ago when I was on a project that required passing safearrays to C++ servers by ref.


The problem I have is if VFP can RECEIVE byte arrays. With COMARRAY(), we can pass TO a COM server.

That's as far as I have gone.

Thanks!

Dennis


>Regarding the object browser, I was suggesting looking at the interface to see what what type of parameter was expected, number, string etc., and making sure to pass that type of parameter.
>
>>>Someone said that it is beyond VFP's 'comprehension' for these byte Arrays... true?
>
>VFP8 and later can pass byte arrays by_ref to a COM server. Before that, we were out of luck. No matter what was done with COMARRAY, VFP passed by val only. Drove me crazy about 10 years ago when I was on a project that required passing safearrays to C++ servers by ref.
>
>I can't think of anything else to suggest at the moment, hope you get it to work.
>
>
>Gary
>
>
>>Gary,
>>
>>I'm a little confused by observation 1. Is the size of the array different after the method call? That would seem to indicate a re-dimensioning by the activex component.
>>
>>Hi, I posted an 'erratum' of sorts on Observation 1... the resulting size is the number of elements of the array I created multiplied by itself... if the array is dimensioned with 12 elements (i.e., DIMENSION laFinger[12]), then the size is 12x12 or 144...
>>
>>
>>I don't have much in the way of more ideas, perhaps loading the array with 0's or chr(0)'s before sending.
>>
>>
>>I have also tried the above suggestion - to no avail. Someone said that it is beyond VFP's 'comprehension' for these byte arrays... true?
>>
>>
>>Have you examined the ActiveX control with the object browser to see if that reveals anything useful? I've dragged an interface on to an open prg or even the command window to see what a method wants and returns.
>>
>>
>>I tried doing that, and the PRG window showed a 'class definition', I then put some code in it, saved it, then instantiated it via CREATEOBJECT()... it doesn't seem to response after that... sorry, but how do you go about using the 'resulting' code?
>>
>>Thanks!
>>
>>Dennis