Joaquim I belive you as I said befole VFP is usually unbeatable in data managemnt especially if you are using VFP data.
About VFP death in the past was other saying that VFP was death, the prb know was that it was the same VFP team that said version 9 was last VFP version to be develop and that now their goal is to work in VFP Interoperability and Extensibility.
And this is the true is not a VB or any other guy saying that, you can read this on VFP roadmap.
>...and if you think with your head and not with your heart, and if you live in Portugal (what, i think, is the case) you should not put VFP apart.
>
>I work in a Big Portuguese Company (+3000 employees) but we have hundreds of Points of sale, all of them with 4, 5, 10, 20 people max, and when i compare my applications (made with VFP) with other applications (.Net, Visual Studio, you name it) i feel the King of the World.
>
>And i'm not the only one: last year, one of my clients (also a big corporation) said to me that my development environment was dead and tried to change it to an application made by their own development personel. That application runs with a SQL back end for the data and with VB as the front end. It was in May, we were running the 2 applications at same time, our idea was doing this during May and maybe June 2005, next we would kill my application. The rest my friend is history: we are in November-2006 my application is still running and their application... well, i don't know what happened to it.
>
>The reason was: my application, with 5 years of use, with 750Mb of data, was faster and cleaner than the other. And notice: the SQL data was in a clean DataBase, created for that purpose in a clean server. And that has nothing to do with the other developers skills (it was a group against a solo developer), they're experienced people. I did not won, VFP did it for me.
>
>I don't know why MS don't use this advantage: they are always trying to find another product: the next one will do better. Now we are earing that maybe Visual Studio 2007 will do what VFP do (it is a Kafkian situation: trying to create a product that maybe in the next version will do what the old does now, and say that the old is a bad product).
>
>Only 1 year ago, VFP was dead. So did say VB developers, now VB is dead and none is crying for it. And we know VFP is alive, dying, but alive. And it is dying for 15 years by now. I remember this kind of talks about 10 years ago, 8 years ago, 5 years ago, 2 years ago,...
>
>And in Portugal where you and i live, 95% of the work is made for little business, maybe the rest of the job (the other 5%) is for big corporations, but as you see, i'm working in a corporation and i do not change VFP for nothing.... well, unless MS will force me. And that seems to be the case, but until then...
>
>Joaquim
>
>