In order to prevent the pain that is an unknown user being in a database when I need to make a fix/upgrade, I've built the following into the various databases we use:
1. If a db is idle for 15 minutes, it closes
2. If I want to 'kick' someone, I can do it by setting a field in a table to true
The problem I have, from time to time, is if someone uses Ctrl, Alt + Del and locks their PC/laptop before leaving the building. In such cases, neither of the previous changes will run and I have to wait until they come back into work the next day. Is it possible, somehow, to either:
1. Have Access detect that a computer is being locked and shut itself down
2. Somehow 'trap' the event on the computer itself and then force any open dbs to close?
1. If a db is idle for 15 minutes, it closes
2. If I want to 'kick' someone, I can do it by setting a field in a table to true
The problem I have, from time to time, is if someone uses Ctrl, Alt + Del and locks their PC/laptop before leaving the building. In such cases, neither of the previous changes will run and I have to wait until they come back into work the next day. Is it possible, somehow, to either:
1. Have Access detect that a computer is being locked and shut itself down
2. Somehow 'trap' the event on the computer itself and then force any open dbs to close?