Ed,
Is this an interface limitation of DCOM or all COM?

The reason I ask is because I have an Excel application that creates an instance of a VFP COM server. It calls a method of that server and that server returns an object with an array property. The Excel application receives the VFP custom object with no problems and the array is usable by Excel.

>>Hi Ed
>>Thank's a lot for your Help
>>
>>Do you know if the New version of VFP can give us this new feature ?
>>
>
>I haven't looked, but I doubt you're going to be able to pass a native VFP object through a COM interface, any more than you can pass a VFP cursor across a COM interface.
>>
>>>It's not going to work; the simple explanation is that there's no COM datatype which corresponds to a VFP object, which would allow it to be passed across the DCOM interface (the proper term is marshalled.) The COM interface is designed to be language platform independent, and unfortunately, there's no common VFP object datatype which could represent VFP's objects; in fact, since there may be non-representable properties of a VFP method (eg cursors), there are potential portions of a VFP object variable that can't be passed at all.
>>>
>>>If you desperately need to pass multiple data items to a COM method, DCOM or otherwise, fill an array and use the COMARRAY() mechanism to permit passing arrays.
>>>