Because of delays in posting changes to .LDB files, it is possible that you might not be able to find all users of the database without writing some code.
The way that I do this is through a startup form.
I created an "Audit" table that tracks users who enter or leave the database through my startup form.
The event routines give me the hooks I need to do this. What I do is make a time-stamped entry of the username during the startup form's Form_Load event. When I close the startup form, I don't actually close it. Instead, I minimize it and make it invisible. But I let it sit there, dormant, inside the user's instance of the application. Then, when someone tries to leave the database, there is an automatic Form_Close event. In THAT routine, I make another entry to the audit table.
This gives me an "In Time" and an "Out Time." As long as no system or network crash occurs, these numbers balance each other by appearing in pairs. After a crash, I might have some cleanups to do.
To find out who is in the database, all I have to do is scan for the startup form Open and Close audit logs and pair them up. If they don't pair up correctly, that person might still be in the database.
