Hi Jos,

Certainly I appreciate civil discussions about experience from people who knew and used finer VFP features, and now use some other tool.

From my VFP POV: I have four basic interests looking forward: hundreds of thousands of lines of existing code, mostly taking advantage of unusual VFP in-line data processing; 64 bit; evolving user interfaces; and protection of intellectual property.

In my case, 100% of main customer base uses Wiindows, usually with more than one HD monitor. This allows consideration of Windows desktop apps that we had moved away from in the late 1990s when we moved everything to the browser. It's possible somebody might want to run one of the apps on a tablet which would be more of an issue for a Windows app... if not for TS that (again) 100% of main customer base already maintains. Meanwhile the desktop app allows multiple communicating forms/windows with split-second refresh that was far more difficult or even blocked in prevalent browsers.

So:

- VFPA and VFP C++ compiler offer 64bit, allowing compilation up to the very latest VC++14 that should enjoy MS support until everybody here is long-retired.

- Evolving user interfaces remain acceptable if you use VFP's Desktop property... apart from half-height title bars that are painted in pre-Metro style, and inability to put buttons in the titlebar (which I know breaks Windows design standards but is used productively by lots of other apps). One solution is to paint your own titlebar, which is the path we took based on an VFPX model. But there's no doubt that the UI is aging as is the IDE for those who still use the native VFP version.

- Moving to 64-bit ends use of existing flls and ActiveX, which is where inbuilt functions for encryption/compression you describe, certainly would be appreciated. However, the underlying code is readily available and we found out how to roll our own in VFP C++ Compiler where it' now encapsulated.

The VFP grid has some nice features but it is aging and I agree it takes work to twist schedulers or treeviews out of it. Having said that, years ago I saw VFP apps making very nice use of scheduler ActiveX controls.

IP protection: a lot of developers say they don't need it... until they discover their work being used or even sold by others without attribution or compensation, or fail a Security Audit because of insecure database credentials or similar. VFP C++ Compiler offers terrific IP protection, moving most functionality into a C++ dll that cannot be decompiled back to source. I'd be interested to know more about WinDev protection.

For the rest: over the years I've remqained a fan of the unpopular Remote View and make extensive use of VFP's direct data munging allowing incredible performance for certain processing tasks covered by contracts that can make you liable for an entire country license if your laxness leads to unauthorized use in unlicensed jurisdictions.

Any insights you can offer are greatly appreciated! - J