>I hope he takes note of the lack of evidence re:VFP
>being a good choice for new development. Trying to
>defend that idea to a potential client will very likely
>result in being shown the (exit) door.

I know several former VFP developers who have this attitude. They're ready to abandon VFP for just about anything else.

I haven't seen another programming language as robust, feature-rich, capable-of-nearly-infinite expansion as VFP. The forms ability itself, with so easily instantiable and programmable custom objects. Nothing else comes close.

Also VFP's native DB engine is blisteringly fast on all but the most complex data usage. For any mid-range app, it is the tool I would choose unreservedly. Smaller apps, possibly. Very large apps, would depend on many factors.

VFP9 works. FPW 2.6 still runs in Win7 32-bit mode. VFP9 will likely run 20+ years on x86-64.

It is odd to me people want to abandon such a powerful tool as VFP because MS stopped supporting it. Many other people and projects are.