>Tracy,
>
>Did you test the compiler or just the extender? If you tested the compiler I'd like to know what else you had in mind.
>
>I'm not trying to be impudent, I'm just honestly baffeled. Using the compiler you can compile your VFP apps and run them as .Net apps. You can compile them as assemblies and then using MonoMerge or Microsoft’s merge tool you can combine them with assemblies written in other .Net languages and using the extender you can have direct access from VFP to all the .Net assemblies. These apps can run on several platforms and if you use strict typing, your VFP code will run 3 to 10 times faster. I have tested this myself and it is truly amazing. You can even debug your applications inside Visual Studio! I just don't get what is left? Not only that, besides 100% compatibility with VFP 9 he is extending the VFP language in some great ways. You will be able to use LINQ inside your VFP code to do things like query arrays and collections. You can have tables that have 1000+ fields and are greater than 2gigs. You can run this code in the 64bit world without having to be in 32bit compatibility mode.
>
>What's not to love? I just don't understand why the VFP community isn't all over this...

I'm quite sure that the VFP community will be all over this in due course.

Speaking for myself:
- I don't yet understand what the "Extender" can do for me (I'm not into .NET at all).
- So far, to me, it sounds like the Compiler is moving along far too fast. There are subtleties in VFP commands and functions that need to be identified/included. And SQL is one COMPLEX entity requiring tons of detailed analysis of both inputs and outputs

Now it does seem to me that those folks are very serious, so I do expect that we'll see something good from them in due course.


>
>Steve