>>>In terms of the fastest SELECT, cursors are generally created the same speed as arrays.
>>
>>Generally, yes, they are. But just to make sure lurkers understand, a cursor can sometimes be stored on disk, which will make it slower than an array.
>
>Creating an array might cause VFP/Windows to page out to disk, as well.
>
>If you use NOFILTER on the SELECT, you're going to get a disk file for sure, which will generally be slower. Otherwise, if the array and cursor are about the same size, I see little reason why one would ultimately be written to disk, and not the other.
Memory structures are different for arrays than cursors. I agree, that with a large array, paging could occur. But I think it is more likely to occur with a cursor because of the way they are managed.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer