Putting the date/time right in the log in table is ideal.
I can just display that table where your "EmpLoggedIn" IS NOT NULL
You mentioned Terminal Services. I have only a few clients using that and there were some issues in 6.5 regarding closing the DB to Reload. (The "phantom user")
All working fine in 7.1 in Terminal Services?
TIA,
Dennis
*****
At 06:09 PM 6/5/2005, you wrote:
Dennis -
I do this with most of my client databases and give them a "Who's in
R:BASE?" menu option. I just create a date/time field, "EmpLoggedIn", in
the table that tracks the user's name or login. Whenever they enter the
R:BASE database, I update the "EmpLoggedIn" field with the current system
date and time. When the choose the Exit button, the program nulls out that
field.
It's especially helpful if users are logging in via Terminal Server, or if
they are located on different floors or buildings.
Sami
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sami Aaron
Software Management Specialists
913-915-1971
[EMAIL PROTECTED]
________________________________
From: [email protected] [ mailto:[email protected]] On Behalf Of Dennis Fleming
Sent: Sunday, June 05, 2005 4:45 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - Logon list
I have an RBase table of all valid users/passwords with their appropriate
"rights" in our application.
If my main menu only lets them exit via an Exit button (no Esc, X, etc.) it
would seem that I can always (usually) show the Supervisor who is logged in.
If you get knocked out to the desktop or End Task, then you would still be
logged in, but at least we would usually know who to contact to log out when
we need everyone out. And, if the same user(s) is frequently found already
logged in when they log in, then we can discipline them appropriately!
Anyone else doing this?
Dennis
*****
Dennis Fleming
IISCO
http://www.TheBestCMMS.com < http://www.thebestcmms.com/>
Phone: 570 775-7593
Mobile: 570 351-5290
Dennis Fleming
IISCO
Phone: 570 775-7593
Mobile: 570 351-5290
