Ravi

The only sensible advice is to STAY PRODUCTIVE. If you already have a VFP version and want to deliver to customers in the near future, VFP is the sensible option.

You hear a lot of positive talk about dotNET from people who have read articles but have not themselves deployed a dotNET app. I have. It isn't easy, it is extremely costly and slow. I have posted elsewhere that a dotNET app we completed can process 1 word document per second on a P4 heavy server, the existing VFP version on my P3 notebook can process many per second. What will your customer think of that?

IMHO this will change. MS isn't stupid, they are learning from our bad experiences and dotNET V2 is on the way. It has changes that improve the business proposition considerably. IMHO you would be wise to look closely at dotNET (and at Java for that matter) once V2 is here.

But don't be stampeded. You do not buy a new car every time you see a model with shinier paint. You consider, analyse, make a decision. Sticking with your existing model is often the most sensible option. Sticking with your existing model does not automatically mean you "have your head in the sand". It may mean you are concerned about the reliability of the new model and want to see how it pans out, or that shiny paint isn't your main selection criteria.

Be assured that VFP will not die tomorrow and it is still as good as it was the day you bought it.

Regards

JR