>>When SQL server became more accessible during the late 90's, I switched my back ends to SQL Server where possible and use stored procedures for CRUD and views and functions for most queries.
>That strategy paid off when I had to switch some of those apps to .NET and could use those procedures, views, and functions almost as-is with the .NET apps, Crystal Reports and SSRS.

Yep, that was all the rage. But typed datasets and SP et al resembled a step backward to some VFP developers who were used to getting change management for free in RVs and total encapsulation of the complexities of the backend: when you update the RV record, only changed fields are updated to the backend, with alerts raised only if those fields changed in the meantime. Not too shabby. Totally old-fashioned of course: reasonably we should not expect to be able to do CRUD without a mainframe-sized Rube Goldberg contraption, right? ;-) The KISS 4GL proposition is so unrealistic in 2015 that you'd have to question whether products like VFP ever really existed if you listen to some people. ;-) Meanwhile back in the jungle, we still use RVs created in a few minutes during the VFP beta in 1995.