My personal opinion is that VFP is a better language, but it does depend on what you're going to do with it. Languages are just tools. Sometimes you need a hammer, sometimes you need a screwdriver. You can use a screwdriver as a hammer, but it doesn't work as well.

There have been a lot of threads comparing the two languages. Try doing a search on Visual Basic.

One reason why I'm fighting to stick to VFP is the UT. This group of people is great at answering questions and I'd hate to lose that.

I think it will be worth your time to learn VFP. It's really not that hard. Learning OOP is really worth it. If you can't find VFP work, VB is easy to pick up once you already know a Visual language.

-Michelle

>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.
>
>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.
>
>Does Visual Foxpro still make sense?