Customarily? I don't think so.

Unavoidably, if you think about how FP tables and SELECT-SQL works. ;-)

Maybe in an internal/desktop environment, but as you move into distributed systems, I think you'll see less and less. I've worked in VFP shops where the goal was to avoid massive amounts of data on the desktop.

That'll be because everybody knows SP is better. ;-)

There are other reasons too. C/S principles say that if all data isn't needed at the client, you don't bring it all down. You bring down the minimum you need to perform the necessary task. But sometimes it *does* make sense to process heaps of data in a middle tier or PC, especially if the resulting calculations aren't going to be saved.

I don't think so. The experience of moving from A to B (be it network systems, service providers, databases, source code systems, etc), where B is both a subset and superset of A, is common enough that what I described is relevant.

It's completely different. VFP has the feature. NET does not. People are exhorted to change. Some people (according to you) say they'll wait until NET is ready. You say this disadvantages them. I say that actually it's like carving your own tabs in FPW shortly before VFP is released. It's not necessarily that smart.

Sheesh, we can agree to disagree.