>> One problem...I may run into some resistance from colleagues, etc. who are less than thrilled with introducing VFP7 into a .NET environment. Most anticipated reaction will be "it's not managed code", "COM is outdated and isn't stable', blah blah blah. <<

What are the technical concerns exactly? Without specifics, it may be worry without any real basis except mis-understanding. VFP 7.0 works great with .NET in many ways. The MSDN whitepaper at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnfoxgen7/html/usingaspnetwithvfp7.asp shows about 4 examples and those examples can be downloaded from http://gotdotnet.com/team/vfp with more information there about this also. It is very normal and common for .NET components to make calls to COM objects and will be for many many years. How can someone say COM is not stable? VFP and a zillion other products (about every Windows app out there) is COM based and has been for many years. Show them the video clip from http://gotdotnet.com/team/vfp of Craig Symonds (General Manager of Developer Tools at Microsoft) talking about VFP7 and VS .NET working together to build modern applications. If you have more specific technical questions or issues, let me know.