>I had resolved to stay out of these endless comparisons ;-) but *finally* I'm seeing a growing sense of dismay from those who try to earn a living using the EF for data. Finally. So in the real NET world there is a mixture of luddites using typed datasets or even untyped datasets with Stored Procedures with no change tracking and various kludges to manage NULL. Sheesh. Then there are people like you using frameworks, proud to avoid the complexity and not knowing or caring what the EF is. I don't blame you, frankly.
>
>My question is: why cannot VFP be seen as a framework that compiles to NET? IMHO people need to get over the Animal Farm "NET good, VFP bad" chanting and review the actual realities out there. If ETC allows compilation of standard VFP progs to NET without having to fight the EF or revert to Soviet stored procedure methodology, how is that catastrophically different from what you hope to achieve with your Strataframe platform?

I bought ETC and follow its progress with great interest. I am sure somewhere down the road I will find use for it. I wouldn't life a finger to get VFP UI if I have .net available, but being able to reuse some middle tier trick will be great. I still want to know everything I can about .NET and I like the stuff Microfour has done with data handling as it is very familiar after working with objectified data for 10 years in VFE.

I honestly don't know if EF is anything I'd care about but I am sure it is being evaluated carefully down in Amarillo and I'll let them tell me when a new MS offering is out of beta <s>