>>>>Hello,
>>>>
>>>>Executable file stored on the mapped network disk.
>>>>After running a while user gets "Invalid Seek Offset" error and programm crashes. Windows XP.
>>>>
>>>>Where is the problem? Network problems?
>>>>Thanks in advice.
>>>
>>>More than likely a corrupted index file. Try recreating your index tags for your data tables.
>>
>>It seeks so, but how index file got corruted? Can it be because of moving from VFP7 to VFP8? Before it such problems didn't occur... :-/
>
>Just because you can seek, doesn't mean it's not corrupted. If you happen to land on a corrupted node during a seek, you can get the "Invalid Seek Offset" error.
>
>There are many reasons that corruption can take place, such as power failures, network hiccups, bad network hardware, like NICs and cabling, need for updated software, etc..
>
>Are you using SP1 for VFP8? VFP8 does a better job of noticing that the files are corrupted than earlier versions of VFP. The corruption may have always been there, you're just now seeing it.

So, deleting all indexes and recreating for all tables will help?