>>>>>>the Entity Framework is pure evil in its current state.
>>>>>>
>>>>>>Yeah. And L2SQL never did and presumably now cannot hope to work with SSCE or any non-MS database.
>>>>>>
>>>>>>BTW, have you checked out Etecnologica? Their latest compiler boasts textmerge, meaning it should be approaching a viable web server option. Theoretically it shouldn't be so tough to create a migration path from WW scripts to NET.
>>>>>
>>>>>Just my guess but I bet it will be a cold day in hell before Rick does more than check out Etecnologica.
>>>>
>>>>Why?
>>>
>>>I know I am being presumptuous by speaking for him. My thinking was this.
>>>
>>>1. Rick is a tool maker, not a tool user.
>>>2. He seems to like things done cleanly, not kludges.
>>>3. He moved on from FoxPro years ago. He was among the first among us to embrace .NET.
>>
>>So you consider Etechnologia's stuff to be a 'kludge?'
>
>That was not the best word I could have chosen. It may in fact be technically elegant. But the last thing anyone but diehards need is a way to keep FoxPro alive. It's way past time to move on.

Your comments continue to eschew your bias towards anything but VFP. The reality is that VFP may indeed be necessary for some of us who have made such a huge investment in it.

In my particular case, jumping to .NET would require perhaps a decade to convert existing applications that are revenue producing and viable for the next 10 years in their current incarnations. And that re-write would generate no additional revenue while admittedly perhaps giving them an insurance policy against extinction.

There are certainly many alternatives to choose from and many of them may be worth investigating before committing to .NET. I don't feel compelled to buy into the MS bandwagon just because they say (or others say) I should.