Well, there's a little more to it than calling a COM object. Why does a Foxisapi type solution get into the docs and not a VFP .COM interop type solution? Has something changed with the VFPT and their direction - again I don't think anyone will blame you for being honest here. Is it because you just don't want to go in that direction or a lack of resources? I'm just looking for a straight answer.

>The VFP documentation already includes information on how to call a COM object, and the Visual Studio documetnation already includes information on how to create a COM object from a .NET class. You won't find solution centric details for application development in the product documentation, that is what the http://msdn.com web site includes and more.

>>Why not VFP documentation since this obviously would be the best place and reach the most people??
>