Who is logged onto my database?

[stuart_adair]

Hello all,

I have a couple of Access databases running on the network at work. A persistent problem I have is wanting to make a change but because people are logged on I cant.

Is there a way I can identify who is logged onto a database ?

Thanks

Stu

 

[vbaInet]

Have a look at this link. I don't know if it applies to your version of access but it might be helpful:

http://www.vb123.com/toolshed/05_map/ch05_backupaccess.htm

 

[ghudson]

The record locking file .ldb will give your their computer names. Open the file wth notepad.exe.

 

[boblarson]

And I hope that you are talking about the backend because the frontend should not be shared.

 

[datAdrenaline]

Check out the utility I posted here on AWF ...

Who's Connected / Who's Logged On

It should handle what you want to know quickly. The utility does not use the .LDB file as it is always added to, but not taken away from. In other works, if you open the .LDB file, you will see EVERY user that has access the database since it was in the opened state. The .LDB files' mechanism for a reset is the deletion of the file once all users are out of the .mdb (.accdb). The deletion is managed by the Jet/ACE database engine.

So .. the utility I linked you to utilizes what is known as the UserRoster, and it is accessed through the use of ADO.

 

[stuart_adair]

Thanks for the replies.
Firstly I havent split the database, its just 1 file. I assume your going to shout now and tell me I'm an idiot - but can you explain the advantages of splitting the database.
I have tried opening the record locking file in notepad but all that returns is the server name where the person is logged on. We have 19 servers on a Citrix farm and the load is spread across them as users log on.

I'm going to work on your suggestions...

Stu

 

[boblarson]

Thanks for the replies.
Firstly I havent split the database, its just 1 file. I assume your going to shout now and tell me I'm an idiot - but can you explain the advantages of splitting the database.

See here for a good explanation.

One of the prime things is to avoid corruption. Access is very touchy and if someone is connected and you experience a network disruption (no matter how brief) you can wind up with a fully corrupt file and then everyone's work comes to a halt. Where if it is split, and each user has their own copy of the frontend, then if one user goes down with a corrupt frontend, it will not normally affect the other users.

 

[AlienRay]

A few years ago, I started introducing a "lockout" function in all my databases. I introduce a linked table that contains just a single record with a single checkbox. Every user module is set to check the contents of this table every time a user opens the database, and every 5 minutes after that. If Access discovers that this box is checked, the user modules shuts down.

I've found this to be a particularly helpful solution when users have left the office, but have left their databases running.

 

[odin1701]

The record locking file .ldb will give your their computer names. Open the file wth notepad.exe.

Not really. But this can help:

http://www.mvps.org/access/modules/mdl0055.htm