YAG,

Gene was so "every-day" and likable that I don't think the VFP community has a good feel for just how astute he was. And with NDAs and such it's really hard to explain, huh? :-)

>Yup - Ken got this right. The big reason for the confusion (I think) is that there's a difference between spec date and ship date <g>. Especially when the first version of .NET was worked on for so long. The nice thing is that internally, every team knows of the other now and ideas pass back and forth quite a bit...
>
>Oh, and the last thing Gene worked on was data/language integration - showing ideas of what the languages might look like. Getting early interest in things that became part of Linq.
>
>yag
>
>>>I have been out of the VFP world for awhile...and now I have reason to look at VFP 9. I've been using ASP.NET for development for the past couple of years. Now that I am looking at VFP9, it's the first time Iam seeing CursorAdapters. This is the same thing as the new ObjectDataSource that is in ASP.NET 2.0! The features and capabilities are exactly the same! I know that the .NET ADO engine is the VFP engine, written by VFP developers, but to see how similiar other things are is pretty amazing.
>>>
>>>If only .NET developers knew where it came from!
>>
>>Hey Harold. Just to clarify some history, ADO (not ADO.NET) was based on the VFP data engine with former VFP team developers working on it. ADO.NET is not based on any VFP code base, it was built from scratch based on a variety of technologies. The VFP 8.0 CursorAdapter class was based on ADO.NET (not source code, but in design). So the 'leveraging' evolution went from VFP 5.0 to ADO to ADO.NET to VFP 8.0. Next (upcoming) is all the new data technologies like LINQ in .NET Framework 3.0 where many things are based on reviewing VFP and other including SQL SELECT native to the language.