Hi N.

This behaviour is an optimizing feature in NT. NT keeps a file open on the server side for a while because it optimizes performance if the client (or another) requests to open the file shortly after it closes.

There is a registry key that controls this behaviour. I don't have the time to look it up, but from the top of my head the name of the key is CachedOpenLimit. setting it either to 0 or 1 disables or enables the behaviour. However if you never have had any problems, its recommended to leave it on.

Walter,


>Hi there! Does anyone know why does NT 4 think that clients (having run Foxpro applications and closed the actual application down) - still some of the Foxpro tables associated with that program still open? Currently, if a user forgets to log completely out from the desktop on client machines, the server still assumes that Foxpro application is still running. Any suggestions on how to get around this? Thanks!!!