Hi Brent,
as for your sample - you missed core features:
Enabling Intellisense by freeing the query from its string (de)limiters and making it native to the language. What arguments get passed to the SQL server behind the scenes is black-boxed by DLINQ.

If you really want to get somewhere near to LINQ, you should at least implement the object syntax with methods like .From, .Select, .Where, .OrderBy, which is an intermediate step in LINQ. Have no idea how difficult or possible it would be to cast this in a real SQL expression.

Guess most of the functionality can / could be retrofitted to VFP, but the question is: What do we gain and is it worth the time and effort.

It´s VERY elegant what Anders Hejlsberg showed at PDC and it´s great they finally take .Net next year (or 2007) further than where VFP´s been for a decade

It´s very elegant to query an array or a collection or just anything, but I can iterate over it very easily too and sort / order it with an old, native function.

Sadly this will actually be the point where we can let VFP slowly retire and leave Ken alone with begging for version X, as adapted CLR languages + .Net will finally be up to and above VFP.

In the Sedna category on UT I asked for making the [] delimiters 'transparent' for Intellisense and syntax checking - as they already are for the pre-processor, finding and replacing #defines, even when in strings - when delimited with []. - Poor VFPer´s LINQ and a possible quick and dirty fix in Sedna.

Interesting times
Cheers
G