>(1) limit the cache

=sys(3050,1, 64 * 1024 * 1024)
=sys(3050,2, 16 * 1024 * 1024)

While that usually is a good idea on pure xBase, SQL suffers [more] if starved for memory. I'ld set the backgroud process to at least 64 * 2**10 as well - that doesn't hurt on current machines and keeps vfp chugging even in background. I find on a decent machine 96 to 128 * 2**10 gives better all around handling - YMMV...
>

>(3) go top, then seek

I often read code going top before scan, locate or seek(). Until now I have not found any issue deleting these [IMHO unneccessary] statements (after making sure no scope "REST" is defined which would lead to a different working pattern if "go top" was eliminated <bg>). Did you find a REPRODUCIBLE scenario where this practice helped ?

regards

thomas