>>>Rick,
>>>
>>>>A client reported that his NT server does not release the databases when my application exits. I created a test executable, that simply opens a database, pops up a messagebox, then closes the databases and quits. When I run this directly on the server, the file gets closed. When I run it from a 98 or NT workstation, accessing the executable on the server, the file remains open until I log off of NT. I have tried this in every version of VFP, and they all behave the same, so I assume it is a problem with my network connection, or the protocols I am running. Any suggestions?
>>>
>>>The NT server, does optimize network trafic. The default setting, I believe, is that NT doesn't imidiately closes the files (internally) when a client closes it. This improves performance when the table or database is used again shortly after the table has been closed.
>>>
>>>However this should not have any effect on operations. There should be a registry key that disables this effect, but unless it causing trouble, there is no need to change it.
>>>
>>>Walter,
>>
>>Thanks for the reply Walter. I looked at the QB article, and I may try that. First, I'm going to try Service Pack 6 and see if that helps.
>>
>>I strange thing about this is that NT only holds on to about 10 of the 40 files that were opened in the app at the time I exit. As soon as I exit the app, 30 files get disconnected, but 10 stay connected, and never release. I've even left my machine on overnight to see what would happen, and the files were still open on the NT machine the next day, even though I had exited the app 24 hours earlier.
>
>There is by default a registry setting with NT 3.51 (not sure if NT 4.0 still defaults it) that, in essence, tells the server to leave open the last 8 files just in case the user wants them again. The idea is to speed things up. The problem comes in when you need exclusive access to one of these files. If the server is keeping them open when you wanted them closed there could be some major conflicts going on in your applications. I believe the registry key is something like CachedOpenFiles. Do a search in the registry editor but remember that even if it doesn't find it the default is to leave the last eight open so you will have to add it to the registry and set the value to 0 to stop it from happening on NT 3.51.

I added that registry entry, but it still does the same thing. However, even though the server shows these files as in use by one user, I can open them exclusively from another workstation. At that time, they disappear from the in use list.