Walter it matters WHEN data comes from SQL starts matering, I tottaly agree with u when u say VFP is the best tool in dealing with data, that's why we all use it and start using it, That I not even discuss.
I've dealt with Data Centric, web, windows and now pocket pc applications, but that doesn't matter.
My entire point and asked for users that was moving to VFP now from foxpro and people starting new Projects with SQL server why where they doing on a language that have been abandon by the manufacturer.

>Alexandre,
>
>I don't know you nor your background, but you clearly haven't dealt with datacentric applications. VFPs strenght is in processing data. Whether it comes from a DBF or a SQL server does not matter.
>
>In VFP you can deal with massive amounts of data without consuming lots of process memory which makes VFP better suited for applications that do need to cache a lot of (meta)data and must run on citrix or terminal server.
>
>When you have to post process data VFP really has an advantage over .NET as it has a very powerfull DML for processing data.
>
>WHY do you think the .NET team is taking VFP as an example to include better data handling in .NET?
>
>Walter,
>
>
>
>
>>Why Peter don't you think when the back end is Sql Server or my Sql VFP looses most of the advantages it had over .NET?
>>And I'm not even talking in spend new development on a language that had is last release with Version 9, since now there is only the Sedna initiative and that will not bring any new VFP versions.
>>I know that there are still people that develop in Cobol and FoxPro 2.6 Dos and Windows.
>>Now do you think that a developer that never developed in VFP that only worked with FoxPro 2.6 should learn VFP now instead of .net?
>>And what about Companies that develop software for commercial purpose like the company I work for do you think they should still do new development in VFP?
>>The company I work for still has the main selling application in VFP but all new development have been done in vb.net some connecting to SQL Server db's other to existing VFP data, But next year we should start rewriting that main application in .NET.
>>In the past our competitors used to say to potential clients why would they go with a product that was developed in a language that Microsoft didn't supported anymore and that was a lie at that time, you can say even now is a lie, but I saw the Writing in the wall 3 years ago on my last VFP devcon I went in palm springs, by then I said to my boss and people that worked with me that VFP8 that was launch on that time was going to be 1 of the last vfp releases and I was not mistaken.
>>I know I'm opening the Pandora box here and that allot of people will be hammering me, cause of the VFP passion, but I always beloved in the best tool for the work and in my opinion and I'm entitle to have one even if everyone disagrees with it, right now VFP is no longer it and I don't understand why new people that want to start an application from scratch would do it in VFP.
>>
>>>>Oh boy i'm going to start a new discussing but I can't let this pass.
>>>>And in the case where we have people using VFP to connect to SQL why are they using VFP and not .NET?
>>>>
>>>Why should they. Do you REALLY think .NET is better at DB application?