>Craig-
>
>Let me start by saying that my current knowledge of COM objects is limited. I understand "custom ole classes" to be VFP's implementation of COM. I have used custom ole classes, but I'm not sure if I have used it appropriately or to its fullest extent. I have never used it with cross-language implementation in mind which is what I understand to be the cornerstone of COM.

That is one of the big things with COM.

>
>Within VFP, should I be able to create a custom ole class that I can code in VFP syntax just like I would code any other object in my application, or do I need to be bear in mind the object model for COM? When I call my VFP COM object from another application written in a different language, will I be able to use COM syntax (if there is such a thing) to manipulate the VFP COM object?

You use VFP code. COM is compatable at the binary level. Your DLL will be compiled, so the application that calls it doesn't need to know anything about VFP. However, the Fox runtime will be needed on the PC that runs the DLL. There is a new, smaller runtime coming soon that doesn't have any of the UI components.

>
>I guess I just don't understand the COMcept of it all? If you have had much experience with COM and know the potential benefits of implementing COM, please share your experience with me or point me to a source that will educate me on the topic.

Start with the Microsoft COM website, www.microsoft.com/com. Read the info on the VFP web site about MTS. It takes sometime to sink in. COM is a complex topic, and will become more important. Probably the best book out there on COM is Designing Component-based Applications from MS Press. However, you need some understanding of COM before tackling this book.

>
>