Ken

>>In the future for .NET programming, possibly VFP-like commands and other data-centric language constructs, but they may not match the same exact name and syntax as VFP uses.

That's just fine. the APIs currently used to interact data in dotNET are described as "obtuse" in the article referenced at the start of this thread. That's a great description. Possible, but ... obtuse.

If more VFP-style functionality is added but with different names or syntax, I'm sure that everybody here can cope- especially if they have a good framework. I'm equally sure that gaps can be filled by creating classes that mimic VFP syntax for those who want to land running.

So this is all good news IMHO.

Regards

j.R

P.S. : once before somebody scolded me for referring to a "framework" when dotNET itself is called a "framework". I'm referring to a 3rd-party addon that creates order with stereotyped functionality and automation of repetitive tasks in a consistent fashion.