>>Personally, I do not see a very good case for having huge result sets that need to be processed in VFP. The last huge VFP-database I got lies many years behind me. But again I realize there might be certain cases that might justify doing that. However in general it should not be done. SQL server is cheap, robust and fast.

We work with static lookup tables with tens of millions of rows. Not live data. We could do intensive processing at the database server, or we could cache dbfs locally and use the power of a modern Windows machine to crunch through it with zero impact on other users or server. We prefer the second option that allows us to do real-time checks that some other vendors insist is impossible.