>Hugo,
>
>First, Jay's earlier posts state clearly that his organization has decided to move from FoxPro, to either Java or C#...period.
>
>Each platform has its own special capabilities. One example, .NET offers full support for interfaces - this aids in OO design/development, and reduces the need for run-time evaluation.
>
>MSFT is moving to a managed code world. Other companies and products (Avalon, SQL Server, Oracle, DB2, Fujitsu, Borland, Activestate) are on board with the .NET platform. VFP simply doesn't fit into the managed code world. VFP COM objects can't be debugged from external apps. The .NET debugger allows you to step through T-SQL stored procedures, Managed Code, C++ code, etc. .NET supports remoting using managed code.
>
>It's all about the platform, the platform, the platform...
>
>Kevin

I was not referring to Jay's post, but yours.

By the way, interfaces, as used frequently, do not aid in OO design/development at all. Interfaces, in the most commonly used way, are just a workaround to the problems that arise using types in an OO language.