>>"Nothing runs like the Fox" was the Kool Aid we all drank back then.

And it was pretty tasty!
With all the choices we now have, we tend to forget that before SQL Server, MySQL, et al became so accessible, there really was no better way to store and access data than Fox.


In my current world, the typical application is CRUD and display a result.
After a couple of years of doing that with .NET/SQL Sever apps, I can't say that the user perceives that they're any faster or slower than the equivalent app was with VFP, because as Rick said, the limiting factor is I/O and UI.
I've come across some real VFP resource hogs (some of my own making) but that was usually a function of the design, not the language.
I just finished an app that has to sum 270K records in a SQL table.
No matter what language I use my best time for that app will be determined by the speed of the hard drive on that server. Because of caching, etc, the effect of the language will probably not be perceptible, unless I made another design blunder.

On the other hand, anyone who had to solve linear equations all day long, and chose VFP as the language to do it with, deserved it!