>>>>>Yes and no. If the file is opened locally, then it is opened by the current logged on user.
>>>>>
>>>>>If it is opened by somebody else, from a different computer, then it has to be opened via a share.
>>>>>
>>>>>Vlad
>>>>>
>>>>>>Always a gothcha! Thanks for the further info, Vlad.
>>>>
>>>>If the local user opens the file via the share, do they show up? I don't have access to an NT server to check this at the moment...
>>>>
>>>
>>>Yes, at least in svrmgr.exe when the file is opened by UNC.
>>>
>>>
>>>>Thanks,
>>
>>Thanks, Ed. I normally use svrmgr.exe to view these type of things, but I had just ran across this winfile.exe tip, and thought it might be useful, too. Do you know how long NT continues to say a file is opened by a user, even after they log out? Files show up in svrmgr.exe for quite awhile even after a user has logged off. (NT4, SP3)
>
>It could be as long as the time to update the Browse List at the Master Browser and propagate it to the PDC if the PDC isn't working in that role; a long time if a station drops out of the network abruptly at least. As I recall, the interval can get up over 10 minutes in some cases, but it's been a while since I looked at it.

I've never timed it, I was just wondering. I have no idea if it's longer to remove a crashed workstations' files or when they logoff normally. It does seem to know the difference between the two conditions, especially if there is a lock on the file. A crashed ws keeps the locks, while a logged off one does not, even if the file still shows in the list.