Fabio,

Just one thing: please don't repost the whole thing, just to make one point...

To your answer: Why should everything be done at once? It's a first step, and it helps in simpler situations. Microsoft also wants to sell MS SQL licenses ;-).
As foxpro has it's roots in dBase, why must it support (all) (ANSI) SQL at all?

VFPT has a smaller budget than the teams of other .Net languages. .Net interoperability was enhanced, SQL was made more ANSI conform, new field types were introduced to keep a good interoperability with vfp and ms sql server, to be able to create remote views on blob or varchar fields, eg...

If you want better OOP, use Smalltalk, if you want better SQL use MS SQL Server or even Oracle. If you want to make applications use VFP.

Your first mistake was to install windows ;-).

Were is the WishList, when you need it? There was one for VFP7, and in the fox.wikis.com I've seen one for VFP8. Ah, yes, and here is the one for VFP10 (if that is ever built): http://fox.wikis.com/wc.dll?Wiki~VFPVersion10WishList~VFP

Take a look and see what problems and wishes people have with/for foxpro. Hidden Properties and SQL speed are not top priority to thos ewho know, what can be done...

Bye, Olaf.