>>One of our customers is getting an "Invalid Seek Offset" error on two of their workstations. I don't yet have any more information than that, except for the fact that the other 650+ customers do NOT get it. MSDN help gives me this:
>>
>>Invalid seek offset (Error 1103)
>>Record your recent actions while using Visual FoxPro and then call Microsoft Support.
>>
>>Which is of no help whatsoever. Anyone else gotten this error? Any tips/hints/suggestions?
>>
>>Thanks!
>Scott
>
>Sounds like your index has become corrupted, DELETE TAG ALL and then reindex.

You mean, rebuild the indexes - after DELETE TAG ALL there are no indexes to reindex.

First I thought this can't be indexes, else more users should be experiencing ICE, but then these two users may be specific in accessing a certain index node in one of the indexes that the others don't, so they step on the error others can't find. If that is the case, rebuilding indexes should help.

Another thing which comes to mind could be their local foxuser files - zapping or temporarily replacing them with a copy of someone else's foxuser file may do it.