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

This last statement is total nonsense. There are many tools equally capable and better. Personally I am using WinDev. Supports forms like VFP, control - field binding and much more.


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

WinDev connects to any database natively/directly including VFP/dBase AND has its own DB engine in both classic mode and client/server mode. And surpases all VFP database limitations and very fast.


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

WinDev creates true 32 or 64 bit applications for Windows, Linux. And also mobile, Android, iPhone. And web based. One language.


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

Because there are better development tools with superior IDE interfaces, developer aid tools, etc. I am not familiar with them all but the world has certainly moved on. VFP is fantastic and we have developed many winning applications and still do and I'm grateful for what we have been able to do with it. But for new project developments, VFP is not the tool of choice anymore for us.