Who's in the database?

[Dave]

Access 2003

Users must login using Access security
potentially 20 + users but in reality one 2 or 3 in at a time
DB NOT split

Problem is I sometimes come in early to do a little development and I can't
access anything because someone has forgot to close the DB the night before.
I have to go to every users machine, log in to their machine (or change
their windows password) and see if they had the DB open.
Sometimes I just feel like to a hard shutdown on all the users but.... well
that is another story.

NEWay: Is there someway I can "easily" find out who is in the DB and only
have to deal with going to their machine.
Does not need to be anything fancy.

Yes, I know - there are clearly multiple other issues here that I should be
considering but for now - I just want to know who is in the DB.

Any help here will be appreciated.

Thanks in advance

Dave

 

[Jerry Whittle]

Right click on the LDB file with the same name as the database. It's in the
same folder. Open With Notepad (but remove the checkmark for Always Open...).
You might be able to tell who is in the database.

But you really shouldn't be messing with a production copy of the database.
Having a development copy is much safer. At the very least you need to make a
complete backup of the database file before messing with it just in case
something like a new update or delete query goes badly wrong.

 

[Tom van Stiphout]

Here is a more elegant way to read the ldb file rather than opening in
Notepad:
http://support.microsoft.com/kb/285822/

-Tom.
Microsoft Access MVP

 

[PieterLinden via AccessMonster.com]

Access 2003

Users must login using Access security
potentially 20 + users but in reality one 2 or 3 in at a time
DB NOT split

This is a recipe for disaster... you are aware of that, right? Also will
cause lots of unnecessary network traffic... be kind and split your DB. Tony
Toews has a nice utility on his website that distributes the new front end...

http://autofeupdater.com/

I know this isn't directly answering your question... far from it... but you
definitely don't want all your hard work blowing up because people are not
using the DB the way they should...