I don't like the method recommended by Nigel. If some line does UNLOCK ALL, it fails. Look at the KB article, "Limiting Simultaneous Users", on my web site
>HI!
>
>I have a function called users in system:
>What it currently does is:
>on the server I have a PROFILES folder
>PROFILES -
> USER1
> foxuser.dbf
> USER2
> foxuser.dbf
>
>The program checks all user folders and tries to open the foxuser.dbf excl
>If it fails then the user is assumed to be in the system.
>
>This solution usually works but often it shows some users which left the system
>I think NT holds the files as a part of it's file caching therefor the excl call fails.
>It seems this way because you also cannot delete the file at this time.
>
>Also it sometimes fails to pick up some users (I dopn't know why)
>
>What I am looking for is ideas on how to show the users that are in the system...
>I used to have a login table with a record for each logged in user but when the program crashes
>this record is not deleted and it appears there are users in the system.
>
>What do you people use if anything for this type of function?!?!?
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer