>hi,
>you mean i must change vfp to vb,vb.net..etc.

No. You asked why MS does not promote VFP. One reason is that MS simply make much more money if you sell a .Net solution using SQL and all the other latest goodies that it sells. They promote whatever product makes them the most money.

iro whether you should change or not is an entirely different question. You must use whatever tool you need to use in order to be succesful and which you enjoy. If your customers only want .Net then your answer is easy. If like me and many others you develop custom, shrink-wrap apps and your customers dont care what your product is written in then use whatever works for you.

VFP rocks dude and I use it because it does everything that I need it to do and then some.

Please dont confuse the .Net, VFP, J2EE, or whatever dev tool issue with one of "what's best". What's best is not always (usually?) relevant in the commercial world. You must use what works, not just technically but commercially, for you and your target customers.