Neil,

>Native data handling is a matter of interpretation. ADO support is built into the BCL, to any .Net language it would appear as a native solution in a similiar fashion to MFC's ODBC support.

Yes, system.data.ado and system.data.sql are built in to the .NET framework. The question being considered is whether a CLR version of VFP would lose its data-handling commands. If some way could be found to translate all of them into ado by the compiler, the question is how much speed would be lost.

>You can again use the BCL System.Reflection.Emit Namespace in conjuntion with classes such as MethodBuilder, LocalBuilder and ILGenerator. This is not exactly inline command expansion but the end result is pretty much the same, dynamic runtime code generation.

Any idea of the speed of that approach? Have you seen any examples of runtime create-compile-run posted anywhere? I'd like to take a closer look at this.