>Peter,
>
>Thanks for the reply. I'm slow responding as I was out of town.
>
>I had the same thought that the VFP users would be the first to notice and that did not seem to be the case. The network tech person felt there were unreleased file handles accumulating that were causing delayed problems.


Larry, though I personally never have heard of this, it is true that in circumstances files won't be released by NT4. I mean : nobody in the system, but NT having the files still open, resulting in a necessary Clear Resources at the server. This obviously could (should) lead of NT having the filehandles obtained. And possibly your network tech doesn't have this feeling out of the blue ...
Sadly, I never learned what is (was) the cause of this, and I recall it only from some two years ago (users calling that they couldn't get exclusive access to files when everybody was out of the system). It would be my guess that some patch exists for NT4-Server, and that by now every customer of mine applied that (without us knowing). Or they switched to W2K etc ...
I'd say, look for this patch (and don't get confused with a similar patch for WTS, because that surely exists ... You don't use WTS do you ?

Peter

>
>Thanks for relaying your experience.
>
>Larry
>
>>Lawrence, just don't believe the story about the 6 handles.
>>We use above 200 handles in 100+ user systems, and there isn't a problem with it.
>>
>>When the workstations are NT (as well), I don't think you even can adjust the max number of handles. W95 etc. it can, and it won't be Fox destroying things. However, when some other app doesn't anticipate on too few handles properly ...
>>
>>Also note that if too few handles were the issue, it would be just your VFP7 users screeming to you first. Well, do they ?
>>
>>HTH,
>>Peter