Adam,
IMHO you can have problem with such complex types as array. Look.. the COM need self describe all property types .. function types, parameter types... how you can describe VFP array? The type libray can't handle such complex (or unknown) type.. (vfp array might have one column as string.. another as boolean.. next as integer, ). COM is language independent .. then.. VB client or another must have same possiblity to call functions or using properties. VB array is not VFP array. Sure, the VB client can't handle type of VFP array..because it will described wrong in type library. I thinking same with VFP client.. because for DCOM you must register your typelibrary on client side.. it must work as stub to remote machine..
My point.. for COM (and private case DCOM) need to use simple types.. If you need pass array.. you can use COMARRAY().. but easy to pack array to XML and send as string..
as output.. pack array to xml and send as string back to client..
Bad case there.. you must describe in documentation a method about how you packing array to XML.. (if someone will write client for your COM)...

Its my minds
If someone have a comment to my reasonings, please leave own notes.

Denis


>Many thanks Denis what about multidimensional array ?
>
> best regards