>>Hi Mike,
>>
>>indeed. If you read the MSDN overview on the Entity Framework, it talks about solving the "impedance mismatch" (their term) between data and objects. And the MVC framework is yet another attempt at the same thing. Just as Linq was. Just as ADO.Net was. VFP has no impedance mismatch, of course.
>
>I assume that is tongue in cheek as you know the "impedance mismatch" has nothing to with language but is rather a question of conceptual modeling. One of the first WTF's I encountered as OOP was explained with VFP 3.0 was that the "objects" that were being described did not map to the normalized relational database model we had grown up on. If that "impedance mismatch" was magically solved by our magic Fox I must have missed the memo <s>

Not really, but neither did stored procedures in statically typed languages (Java for Oracle / C# for MSSQL) nor did xpath or
entinty framework from what I have heard so far.

IMO, Only real solution for this 'problem' can be found using dynamic languages.
FoxPro is dynamic, fully OOP language built with noting but data in mind originally, so I wld say that fox offered the best chance ever for resolvng this 'problem'. If not teoretically - then at least practically.

In other words, solution developers wld have had much easier ride if FoxPro was alowed at MSSQL server side as language
for writing stored procedures, components, cushioning impendance mismatch, and many other problems, then they have it right now, with sterile/obnoxious NET# that hates its own momma (let alone our data and real life problems) {vbg}

Cheers :)