>I am a FoxPro 2.6 programmer. I realize that I must move to a new technology, and at first VFP seemed to be the obvious choice. But after further research, I realized that it means learning what is essentially a new language and a new way of doing things.

Yes, Visual FoxPro has a learning curve. This mostly relates to the full OOP support environment and a lot of new technologies now part of the package. Which means, a new way of thinking and doing things. But, what wonderful power you would end up with. :)

>If I am to go to all of the touble of learning a new platform, why not switch to a RAD language that is more commonly used like Visual Basic? In the bargain I will be learning the same language used for other popular products like Word, Access, and Excel.

Yes, Visual Basic is more commonly used. I also use it a lot for various robots, etc. However, it's not RAD. That's why you have almost no RAD tool for VB. One thing which makes it's difficult to have RAD tools, is the non OOP support of the environment.

>Does Visual Foxpro still make sense?

That depends on your project. I always have to evaluate the project scope and deliverables before taking the decision on what tools to use.

Personally, when it concerns a full blown database application, I don't have any doubt of the power I'll get from Visual FoxPro. When I need some non full powered database applications, robot applications, DLL, ActiveX and other fancy stuff like that, I go with Visual Basic.

That also depends on your client environment. They may have some strict rules for what tools are allowed in their business approach. ;)

Good luck