>We are about to embark on a major rewrite of two of our legacy procedural apps, one in VB, the other in VFP. The rewrite will combine the functionality of both apps while keeping the look and feel of the VB product (based on customer preference for the UI).
>
>We have decided to build it using an N-Tier component based structure. A lot of the business rules are data driven from existing extract driven foxpro tables. We are looking to do a proper object model for the various business and interface objects we will be designing and need to develop the COM objects in an OO language. My boss and my other team members are leaning toward using VC++ for the object programming, but I have concerns about the level of complexity we will be encountering and the learning curve (none of the developers are expert in C++ and will have to learn the language as well as COM). I think we may be better off using VFP, since I have a lot of VFP experience and my other developers have intermediate to advanced VB experience, but there are concerns about performance, scalability, etc.
>
>Any advice from those that have been down this road would be appreciated.....


Doing COM development in VC++ is ugly. You have to worry about lots of details that VB or VFP handle for you. I suggest you look at COMCodebook (www.comcodebook.com). It's a VFP framework for doing n-tier applications. It handles lots of the middle-tier details for you.