>>>>agreeing with you in tendency (less acerbic) on the other points, but
>>>>
>>>>>VFP's data handling is an anachronism when using a server based database.
>>>>
>>>>Why ? Having the backend where-specified data mirrored in equivalent tables to feed the biz objects
>>>>IMHO is more sensible than EF or other ORM frameworks (nHibernate or what do you use ?).
>>>>Especially if you are fluent in SQL, why for need 2 different ways to access data ?
>>>>Do you prefer LINQ vs. SQL, as it again puts you into a MS-controlled niche compared to SQL on nealy all backends ?
>>>>
>>>>The local cursor engine (pls separate from dbf as backend data store) is the thing keeping me with vfp -
>>>>and is the thing making me look at Lianja, as today there is no client financing a cursor cache layer
>>>>with SQLite having update automatics similar to Ado.Net or vfp-Cursoradapter,
>>>>which is what I'd create to scratch my itches.
>>>
>>>In .NET you have local tables you can manipulate. You can use LINQ on them. Not quite as easy as VFP cursors but they are functional.
>>>
>>>Again, I do my data manipulation server side if at all possible.
>>>
>>>
>>
>>PMFJI; over the weekend I read a tutorial on Entity Framework and it sound (the tutorial was not very clear on that though) that you can't use EF without LINQ. Is this correct?
>
>As far as I've seen, everything you do with EF revolves around LINQ.
>
>I was originally pretty excited about EF, but when I realized it didn't handle Stored Procedures w/o a lot of under the hood work I gave up on it. The benefit was not worth the cost since I use stored procedures a LOT.
Thank for confirming my understanding.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham