There are NUMEROUS threads here on the UT regarding this error. As a start, run the app using a mapped network drive and not the UNC path (for troubleshooting purposes). I found that resolved most of the problems and I could then start narrowing down the other causes of the 'Invalid Seek Offset' error...

Invalid Seek Offset Thread #1153903 Message #1153903
Invalid Seek Offset - reproducible Thread #1137918 Message #1137918
Invalid Seek Offset Thread #983822 Message #983822
Invalid Seek Offset Thread #949098 Message #949098



>I am using SQL Pass-through /Remote views to access SQL Server database.
>Users run the application from the desktop shortcut pointing to the standard VFP9 SP1 executable using UNC path on the server. (i.e. \\myserver\software$\MyFoxApp.exe)
>
>First week on the client site went ok.
>
>Second week there were 2 crashes with the error message “Invalid seek offset” (please note that I don’t use indexes, just remote views)
>
>Third week (now) they have problems all over the place.
>Error messages “Invalid seek offset” and “Not enough disk space for \\myserver\software$\foxuser.fpt” (there is a plenty of disk space available)
>
>This all points to network problems. I have problem convincing the client that network needs checking. (the same exe and same approach works fine with other clients for months)
>
>Can someone please, point me to the article or facts that will help me to convince the client that they have network problems, or maybe I am wrong?
>
>Thanks in advance
>
>Zoran