Yes. Yes.
How much coding do you do?
There are a couple methods I can think of to get the system to shut down after inactivity. I am wondering if there is anyone with a more application specific method. The problem is deciding what constitues activity.
As for user security, how are you implementing this? It sounds like you will need to store values on the back end. In a user table, create credentials that is not linked to the front ends, so users can mess with it, and then set a value in the table when a user is logged on. If someone else tries to log in with the same credentials, just check the value, and if set to Yes, for example, prevent login and pop up a message box instead. Pretty simple if you are already doing security. How are you doing security?
mmcdonal
|