>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?


I agree whole-heartedly with Michel's response and wanted to add just quick addition -- I've been doing FoxPro since version 2.5 up to 6.0 , and it by far is my tool of choice. I am however currently learning VB siimplly because it does have advantages in SOME areas as Michel described, notably ActiveX and interrnet technologies, although VFP's interenet support has progressed considerably in the last two versions. My point to responding to this thread was this --- as I'm learning VB, the more I'm extremely disappointed in it's support of Object Oriented Programming techniques. Yes you CAN incorporate these techniques, but it's as though this support was added as an afterthought to the IDE, and at this point seems much more difficult to implement than VFP. And learning OOP methodologies is essential these days, no matter what tool you go with.

You would already have a headstart with VFP, since a lot of the language syntax hasn't changed., and VFP's IDE extensively supports OOP programming techniques.
I will say this--- the client in the end usually will decide this for you-- I'm a consultant working on a project here locally for a company and was brought in to convert legacy FPW/FPD programs to VFP. BUT, I am rewriting two other applications in VB simply because the company dictated any new development would be in VB. Go figure....

[shrug] One of these days Visual FoxPro will get the respect it deserves....

Hope that helped

sc