>>In the beginning of the year I spent much time trying to resolve errors of "Invalid Seek Offset" and "Error Reading File" that occured at only one client location. I never did find the problem then... but just yesterday I found this out...
>>
>>I opened one copy of VFP to access data across our Novell 5 network to do some testing on a login exe that updates local workstation driver tables with their network parent. I opened a table contained in the database from the command propmpt and thus opened the database also. I then logged in again to cause my script to call my VFP exe. When the login was complete and I returned to vfp and tried to use the same table (which I had closed, but the database was still open) I received and "Invalid Seek Offset". Now I had another VFP window open that I was using but I had closed the database there and all seemed fine. So I theorized that when I logged in again, Novell logged me out first and then back in thus changing some sort of datasession ID or something... So all of a sudden it occured to me that if a user temporarily got disconected, but was reconnected without their knowledge via Novell's autoreconnect that subsequent program calls to tables in the already open database would
>>cause an ISO.
>>
>>So the question... Is there a way to monitor the for loss of connection and thus compensate for it when novell automatically reconnects? Or is there some sort of datasession ID that needs to be fixed in the datasession object?
>>
>>All thoughts, theories and guesses are welcomed.
>>
>>Shawn Burke
>
>So, to summarize:
>- you logged in to the Novell server
>- you opened a table (and its database, implicitly)
>- you closed the table (but not the database)
>- you re-logged in to the server (which if past experience is a guide, implicitly logs you out, then back in again)
>- you found problems with VFP session #1
>
>This can't be too surprising. Getting implicitly logged out is no different from shutting your machine off, or yanking out the network cable, while files are open. Basically, all bets are off.
>
>Even with some "auto-reconnect" feature on the server (whatever that means), if you've logged out you've explicitly told the server "I don't want this connection any more" and the server isn't going to take any pains to preserve it, or any files that may have been opened in it.

Okay... so now what can I do to catch this, alert the user, and close the program back to a safe state?