Come on Dragan,

>With this product, several mantras which were set in stone in 2000 just fall:
>
>- ADO.NET is THE data provider in dot net, and we don't need no other way of doing data
>- VFP can't be 64 bit as that would require a major rewrite with unpredictable results
>- VFP can't do more than 2G per file as that would require it to go 64 bit
>- VFP.NET would not be VFP at all, it would have to lose its local data engine

please be a bit more fair to MS:
in their latest descriptions of the problems they cited ROI as the biggest stumbling block.
When it was decided that vfp should stay out of .Net, .Net was not really there!
MS hiring Hugunin for Ironpython marked a rather drastic turning point - and Hugunin had already created Jython, which at start had been deemed impossible as well, at least to be in the same ballpark as CPython.

>All of those now look like political decisions, not technical roadblocks at all. Emperor's clothes look a little odd, too.

MS is a business and most of us are earning money as well, even if we sometimes give routines to the public. I thought MS was quite open in describing the real issues.

regards

thomas