>>>How do you detect if the user is still in the system or just logged out improperly?
>>
>>OK, you got me there :) But in this case you can incorporate what
>>Alexadre suggested along with that Logging function: set a timer to
>>post LogOut value every 5-10 min (or whatever is most applicable) and
>>add bit-field with .T. if the user logged out, and post .T. to it only
>>when the user actually loggs out. If at the time of checking for user-crashing is more than the time set and the value of SuccessfullLogout
>>is .F. - the user happily crashed, else - he's still on-line :)
>>
>>How did I get out of this one, huh? :)
>
>Hahamm... You forgot to add the sugar and spice... Mix it all up and you'll get a beautiful cake... :-)

Hey, at least it will tell me exactly what I am after! The OTHER
suggestion about leaving the TXT file open for the duration of the
session first of all unnecessarily takes up a file handle per user,
second - still requires a table to maintain. Why not just maintain
that table in the first place?...But speaking about sugar and spice...
You made me remember that I haven't had my coffee break for more than
an hour!!!! That's a NO-NO with me!!! Be right back, might come up
with something else :)