>I've thought about this, but it's not very practical, since I have to wait an hour or so into runtime to see what works and what doesn't. But to analyze this, I start with about 19MB default foreground...The app itself needs only a couple MB including the cursor & vfp needs. The large table index takes about 5 MB, and the large table itself is currently 8 MB but both these will continue to grow gradually in size. The cursor will not grow very much. Any recommendations for these circumstances?

May not be practical, but I belive it will solve your problem. You don't have to wait the whole time, just till it slows down. Then, exit out and try a lower number.

Also, you will have to do this differently on each machine too. But, is it worth it to get the ap to run as fast as possible? Why will you spend a day changing code and trying it, but not this?

BOb