Mark,

It shouldn't be VFP which keeps the indexes around, even after exiting and restarting it (and yes, I saw this same warning in the recent FPA article on 'More is Less with Rushmore').

Most likely it is Windows itself, recognizing that the file is still intact and unchanged from last usage, so simply pointing to the RAM area again.

Cheers,

Jim N

>>>Is it possible to access and store the actual query time from a VFP SQL query?
>>>
>>Sure,
>
>Be careful analyzing results if you are designing for a slow network--you may get very different results between your first and second query. VFP is very good at keeping index information once it has loaded it. Even exiting VFP doesn't clear the info.
>
>For example, on a particular view I was recently testing, the first time I use the view over a 33k modem connection it takes 60 seconds. The second time is 2 seconds.