>They've been saying "no future of VFP", I do not think anyboddy in his right
>mind would discuss that the future of VFP is "doubtful", or put differently
>would _you_ bet the farm on it?

Yes, actually I would. In fact, I more or less have, since VFP is the only modern language I'm conversant with. While I would have no trouble picking up a new language, it would be difficult to convince a new company of that.

>This strategy would have made sense if the first stage could have been done
>reasonably fast. But to my disappointment, there is a major price to pay in
>terms of development time if one wants to go OO.

Of course. You can't just do a conversion to OO without planning it out first, and finding the places for re-use. The conversion from procedural to OO is as large in VFP as if you converted it to a different language, except that you get to reuse some, but not all, of cour code. It's later in the project when you save your time, not the first stage....

>For smaller projects, I will continue to use VFP, so you're not rid of me yet.

Good :-)

>I know that VFP is great, you know that VFP is great, but nobody outside is
>convinced.

That could change, with all the good press the VFP6 beta is getting... Infoworld ran a large, very positive review of the beta, and their biggest objection was that the beta issues needed to be straightened out....