I think you're still stuck on VFP versus SQL Server when many here have delivered apps using both for 20 years. Also the idea that a particular 4GL can only ever be used with obsolete runtimes and IL. Do you know what other vendors use to create their C++ apps - or even their assemblies?

>>As opposed to not having to pay an extra 1/4 million dollars to have access to an antiquated desktop app and have a windows admin create and delete user accounts all day long when SuzyQ in HR can do it from a website.

Maybe check out MS revenues from servers and Azure. 46% server growth, 90% growth by cloud division up to $5B sales (compared to Amazon's $20B) but MS saying they're tracking strongly for $20B. They don't call it RDS, but that's how you access an app in Azure.

>>VFP is not VC++, and VFP would be the development language yes? The client will care. Or at least the ones I've known sure care.

No, VFP is an obsolete IDE. For the C++ apps the "language" includes ASM, VC++ and xbase converted to C++ for compilation using MAKE. Once it's a dll an expert can decompile looking for clues as to source, but C++ is C++, it's not distinct IL like your assemblies or a VFP exe.

>>Contractor A: I will write you an app...

While I certainly get your point, I have no experience of this contractor anecdote you keep raising and can't comment, except that in 2017 I wouldn't propose a VFP app for somebody seeking bids for an app they'll own themselves. Though with the furious development churn that goes on these days, were I the CFO I'd be looking for lowest cost for something that may only survive a few years before the vendor suddenly deprecates it or a gaping exploit is revealed in the open source stuff relied on, or a new clever thing du jour sweeps in.