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. 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! 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?!

I agree with DS. Performance depends on lots of factors. One big one is if you need to interface to clunky old unmanaged code- MS Word, for example. ;-) And current Winforms feel slow- just like VFP tabsets used to feel incredibly slow until hardware caught up. I guess we can expect that this time as well.

All the above assumes that performance is a major consideration. In many server apps that can process 100 hits per second, performance is hardly an issue at all.