Identify users with db open

[CanadianAccessUser]

Hi,

I'm wondering if there's any way to find out who has a database open.
I've saved the file as an ACCDE for the users and kept the ACCDB file as my working file. Whenever I make changes to the db I need to save a new ACCDE file on top of the existing one. In order to do that, I need to ensure no one has the db open. Half the time I need to track down 1 of 15 people to find out who it is that has it open so I can kick them out and save.

I don't have any login features, but could use the POD # that each cubicle has associated to their computer if Access allows that...

Any bright VBA ideas?

Thanks,
Canadian

 

[MarkK]

Have you split the DB? The tables should be at a public location on the network, and each user should have his/her own front end program file. Then, each users' copy of the FE connects independently to the BE, and you have a very easy time overwriting each users' FE with the latest version.

 

[CanadianAccessUser]

All users use the same FE, but yes I've split the db.
This leaves me hunting people down.
Usually it's just a good laugh that I need to kick everyone out. The issue is when I can't figure out who still has it open.

 

[MarkK]

Yeah, so, each user should have his own copy of the FE on his own machine. Then you just shut down that copy and replace it, on that one machine, for that one user. No hunting down.

The advantages of splitting the Db are lost if everyone uses the same FE.

 

[Galaxiom]

There is this tool, attached.

Point it to the back end and it will show you who has the front end connected to it. Apparently it can aslo kick them off but I have not tried this.

I don't know where I got it from. If anyone knows who it should be attributed to, please say.

 

[TimW]

I have developed a method to do this based on a search of 'Kick em out'.
I have attached a sample.
Basically each user have a copy of the front end. (If they try to use the original, i lock them out as I don't want the original corrupting. Which happened from time to time)
When I want to shut down the db, I set the flag and give the users a set time & a message. So they know why and when the must log out by..If they dont log out then the database will shut anyway
BTW _ I also have a method of updating everyones copy of the front end, but this does not work on all PC's as it depends on the individual PC's settings. The alternate for this is to ask the users to COPY the new front end from the server.
Lastly, I use the same file name for all updates and I have a front end table and a backend table that i use for version control. Therefore if the version of the db changes I change the backend number and this is then different to the front end - hence users know (and the local db knows) its time to update

HTH

T

 

[CanadianAccessUser]

The advantages of splitting the Db are lost if everyone uses the same FE.

The advantages are not lost as splitting has other benefits.

 

[CanadianAccessUser]

Galaxiom: Your assistance is always appreciated.
TimW & Galaxiom: I will take a look at your zip files then decide which one I want to use. Both appear to do exactly what I asked for.
Thank you both.

 

[CanadianAccessUser]

I ended up getting the Remote close to work it it's marvelous!

Thank you all so much!