***
Another approach (I adopted this one) is to wait and see what the VFP team will do in the next version(s).
***

Here is a question for you: what would it take for the VFP team to do to warrant a wait and see approach right now. I think Kevin is right to the extent that Fox developers are going to have to move. IMO - .NET and VB .NET in particular is the logical place. But that said, Java cannot be discounted either.

I think Kevin is absolutely correct when he says that the "writing is on the wall".

< JVP >

>Hi Metin,
>
>Another approach (I adopted this one) is to wait and see what the VFP team will do in the next version(s). IMHO think things haven't settled down enough to make big investments in new tools (just keep looking around). Meanwhile you can keep geting deeper into VFP.
>
>It's a kind of bet in our own future, as FoxPro developers :)
>
>Regards,
>
>Fernando