>>I need to be able to gauge the performance of a SQL the first time it is issued. FoxPro cached the result and even if I quit out of FoxPro, I still get the cached result.
>
>Hi Dan,
>
>Keep a VERY large table handy and do a select * from handy_table. If the table is as big as the amount of RAM you have, it's likely to flush whatever was cached before issuing the select. Remember that you have to actually ISSUE the select statement. Just USEing the table won't do.
>
>Granted, it takes a while to flush 256MB of RAM, but your benchmarks will be more accurate (or at least behave more normally) if you do this.
>
>Good luck!
>
>Alex


Don't forget the NoFilter. That did do the trick though.