>One of the major differences between .Net and VFP is that even when working against SQL Server the "cursor" in VFP is held in a temporary dbf (which for large datasets we actually point toward an imdisk ramdisk: nothing is faster than memory). In .Net, a recordset is help in memory. That's fine for small datasets, but datasets for reporting (munged from what's available on the backend server) can be quite large. It will be interested to see speed differences between the two approaches.
>
>Hank

That is not entirely correct. VFP might span SQL resultsets to disk, but as long as you don't force them to be written to disk (SYS(1104)) or create an index on it, most will entirely reside in memory. Only longer tables will be written to disk.

You can actually check whether they are written by disk by using

lOnDisk = FILE(DBF("MyCursor"))