>
Oh come on. What about network issues and the rest of it. There are numerous scenarios where persistent local cursors or collections are necessary to function in real life.
>

Sure, but Fox is not the only way to achieve that....

>
In one of our own apps we had a lookup with 40,000 words that is absolutely hammered during processing. SQL Server performance as good as local VFP instances using cursor instances?! No way!
>

Highly doubtful - assuming proper configuation. A properly tuned SQL Server db, with a stored proc, will out perform and will out scale a soluton that relies soley on a Fox dbf as a local data source...


>
It had to be away from the database server using local data to be feasible and scalable. So in dotNET we could load it into a massive memory-resident collection, which *really* impacted performance, or we could use MSDN or Jet... but why? Just so we could use dotNET rather than VFP? And then try to make it perform almost as well?!
>

That would have been the wrong way to solve the problem...