I assume you are referring to an HTML form served by FoxWeb, right?  If yes, then you are looking at the problem the wrong way.  One of the differences between web applications and traditional desktop applications in that the browser does not maintain a continuous connection with the server.  What happens instead is that information is exchanged back and forth whenever a user types a URL, clicks on a link or submit botton, or otherwise causes an HTTP request to be sent to the server.  The server receives the request along with any accompanying POST (HTML form) data, cookies, etc., calls the requested script, sends the script output back to the browser and closes the connection.

 

Once the connection is closed, no additional interaction occurs until the user sends another request.  The server does not get affected by whether the user stays on a form for a length of time, navigates to another site, or even turns off her computer.

 

In the situation you described the problem is either caused by a FoxWeb channel that did not properly close the table in question, or by another instance of VFP, accessing the table interactively.  If you have enabled the Close Tables setting in the configuration screen, then FoxWeb will automatically close all tables as soon as your scripts terminate.  If the above option is not enabled, then it is the programmer's responsibility to close tables in the script code, or in fw_exit.prg.