I realize that this is an old message... but we've been having similar intermittent errors "Error reading file" and "Invalid seek offset" on a Novell network with Novell Clients and Win 98/2000. I have tried changing some setting under the advanced option in the client (increase auto-reconnect timeout, delay write off, etc). does this help? Is there a way to maintain novell client's connection to the server?

thanks

bonnie

>I would also suggest checking for the possiblility of network disconect. I had several problems with VFP and "error reading file" or "invalid seek offset" on a large multi-story corporate office. Extensive researched revealed that the errors were causeed when the novell client loss connection to the server and automatically reconnected (auto-reconnect is an advanced option in the client). When this occured the "seesion id", for lack of a better term, must be lost and VFP doesn't know how to get data.
>
>If you were to pull up explorer.exe after a network disconnect (assuming you already had it open) you'll see the screen refresh. For some reason, VFP just doesn't seem to be able to handle this.
>
>I realize you aren't getting an error message.. but perhaps your error handling tries "RETRY" when receiving certain VFP errors? Thus hanging on the RETRY which never succeed?
>
>If none of this helps, email me personally and I'll send you a number of word documents that I put together on Novell client settings and other "network connection" thoughts and theories.
>
>Shawn Burke
>
>>Anyone have a "tweak list" for Client32 on Win98 machines for a VFP app running with data on a Novell 4.2 server? The app hangs every now and then (only about once every two weeks per user) but we cannot roll it out to the entire company until this is solved.
>>
>>If you do the big Ctrl-Alt-Del when the app is hung, it says that the app is "not responding". By this point though, it is hard to even terminate the process and usually it means a hard boot of the PC. It sortof "feels" like some sort of communication problem with the server since it happens just about always when the user presses the Save button. The app is written using VMP's framework, which has the proper error trapping, but it doesn't even get to a VFP error because the .exe is somehow just hung.
>>
>>Albert