Indeed; and in fact I wrote the lead researcher at Cambridge, letting him know just that; he referred me to Ken Levy, i.e., he didn't get it.

Hank

>-like the denials I had last year about X#, which has now been revealed under another name-
>Are you talking about Xen? See this link http://www.microsoft-watch.com/article2/0,4248,1454549,00.asp
>
>This is from this article
>
>The integration of data access in mainstream programming languages is of particular importance — millions of programmers struggle with this every day," according to a white paper from last year, entitled "Unifying Tables, Objects and Documents," coauthored by Meijer and Microsoft researcher Wolfram Schulte.
>
>With Xen, Microsoft is working to show that it's possible to feature both SQL tables and XML documents as "first order citizen(s) in an object-oriented language," the paper continues.
>
>***
>I find this amusing. The one thing I don't struggle with in my programming language is data access. Also never had a problem with tables not being a "first order citizen" in VFP
>
>
>
>
>
>>We have been told, over and over again, that we would lose key functionality in VFP if it were ported to work with the Common Language Runtime, i.e., the CLR, i.e., Visual Studio .NET. This is because the CLR is not made to be used with dynamic languages. Well, guess again: Jim Hunginin (creator of Jython, which is a Java-compatible Python) has been creating IronPython - a fast Python implementation for .NET and Mono, and is now working at Microsoft continuing that work, and helping other dynamic languages integrate with .NET.
>>
>>Frankly, most VFP developers would be pretty happy with Python. Either way, things are looking up for the longterm future of productive software craftsmanship.
>>
>>Hank Fay
>>
>>PS: I can't wait to see the furor this causes; especially the denials from MS (like the denials I had last year about X#, which has now been revealed under another name but with acknowledged roots in a Cambridge Microsoft Research language called, er, X#).