David,

Even if it can be optimized a bit more, it doesn't change the fact that SQL results are stored either in memory or on disk (for VFP it's alway to disk).

This give the xBase variant a tremendous advantage because it doesn't actually execute the query and uses the original tables online to construct the view (yes, there are paralells to draw with the filtered cursor), saving CPU cycles, HD availability and memory.

You've got just to load the VFP-view and doesn't execute the relations and filter setting for those records you don't access, giving you a tremendous performance gain over very large SQL - views.

Walter,