>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?

In addition to the indexing problems discussed, the ISO will show up for other problems. MS has a KB article describing a problem with one of Symantec's files (PCAnywhere, usually). Also it will occur if you have a bad printer driver or a bad network card. I've seen that twice. If all your users are having the same problem equally, look at your views. If the ISO starts with the same user and spreads gradually to others then check the first user's hardware VERY carefully.

HTH