>I'm a VFP programmer, but I have faced more and more tough reality from the clients, such as easy-to-corrupt, unsecure database, out of dated, discontinued product, etc. I wonder if there any future for VFP? how much people still using VFP with dbf? should we switch to SQL-database to survive?
>
>Jerry

O! GOD!
Another endless thread! NET vs VFP

Yes, we still using VFP with much success that we have 2-3 years ago.
Just use the right tool for the thing.
If you want database desktop application and you needed it NOW use VFP.
If you need Internet application with access to some Databases use NET (and you could use VFP as Data layer just for speed and easy manipulation).
Yes DBFs are unsecure. They are pure TXT files with some header, no encryption, no protection.
If you want more secure database you could use whatever BackEnd dtabase you want: SQL Server, Oracle, MySQL....
It is very easy to build your application that way that backend is not a problem. Just a flag in your setting.
We now can use VFP, SQL Server or Oracle in our application. Just a matter of switch in our INI file (I hate to mess with Registry :o))

With this I don;'t mean you didn't have to learn some other language, NO!
You have to.
But VFP still have a life in it.
You saw VB applications created nowadays didn't you?