>>
>>Agreed. Just IMO, but I think that if I were a VB developer, who knew neither VFP or VC++, and had to produce a COM component, I think I'd find learning VFP far less a daunting task than VC++, if only from the syntax.
>
>Exactly. I don't know VC++, but everyone I've ever talked to that does says you don't want to use it to create COM components cause it's really hard.

Well, I've never tried because I've never had the need. Everytime I've needed to create one, I simply fire up VFP. Part of the reason for this is leveraging existing code is some heavily data oriented systems, that needs to be utilized in other development environments. In some cases, VB may have been a better choice, but, then again, why re-invent the wheel?