SNIP
>
>VFP only supports part of the OOP specification. It's a leg up from VB 6.0, but it's a far cry from a pure OOP language as well. VFP is not .NET--no matter what you call it. We all had our chance to have it included in the architecture, but bygones will be bygones.

Did we "all had our chance to have it included in the architecture..."?...funny how it felt like that was a 'discussion' of a fait-accompli directed by our 'leaders'.

It was very recently that Steve Ballmer said that small/medium business is MS' biggest market segment. As that sinks in at MS there may still be hope to see the CLR changed to support things like .DBFs and to have a VFP server and such. Or there may be other ways to bring VFP into the .NET fold. After all, MS makes these rules up and has the power to do whatever it wants.