>>Some of my users are getting an Invalid Seek Offset when they do an account number lookup after the PC has been idle for an hour.
>>
>>The lookup finds the record in the main table, then requeries three views. The views are indexed, using the 'trick' that I found here on the UT.
>>
>>I know that ISO errors usually indicate corrupt index files. The index on my main table seems fine, so I suspect that the bad index may be on one (or all) of my views.
>>
>>Any thoughts?
>
>The view indexes are not keeping up with the views. Is there the possibility of a requery and a seek without a reindex? There would be your problem!!!

Normally, view keeps indexes until closed, i.e. it's possible to requery() and seek without subsequent reindexing. That's another story that it's more reliable to reindex explicitly in code (anyway it takes the same time).