laccdb - who is in?

ppataki

Registered User.
Local time
Today, 04:23
Joined
Sep 5, 2008
Messages
267
Dear All,

In previous versions of Access I could easily see who is in a particular file by opening the lock file with Notepad
However if I open a 2007 format lock file I can only see weird characters there instead of user IDs

I checked an API called AppUser but it is outdated and does not work with 2007 formats

Could you please advise how I can check users in a 2007 format database?
Many thanks in advance!
 
I use the Explorer, and just look at the owner of the lock file...
Would that yield the same results? I've never used the notepad method.
 
Explorer is also a good idea
however, what do you do if there are multiple users in it and you want to see all of them?
 
to be honnest, i've never come accorss that issue.. I had no idea that you could view them all in the lockfile with notepad, that's neat. I personally don't worry too much about it because my front ends are stored locally
 
to be honnest, i've never come accorss that issue.. I had no idea that you could view them all in the lockfile with notepad, that's neat. I personally don't worry too much about it because my front ends are stored locally

By the way Access_guy49, it isn't just frontends which have the locking file. When you open a frontend and a table gets opened by the frontend in the backend, the backend also has the ldb/laccdb file created.
 
I did know that, noticed it once when i was playing with a front end i was working on. I guess it just never mattered to me because once my front ends are created that means my backends are also created and therefor i really don't care if it's locked because i wont be changing the design of the backend..

With that being said, Other than the ever so rare "Lets go play with the database design" scenario, is there ever a reason why i would care that the backend of the database is locked?
 
is there ever a reason why i would care that the backend of the database is locked?

Well, what if you have to go add a field to a table? Or delete a field from a table? Those will affect you. I've just had to do that for us because we had a new table that had to be added (that can be added without a problem) but a new field also had to be created in another table. So I had to wait until nobody was using it to make the change.
 
Oh, I've always kicked people off the backend when i make changes just for fear of data loss/corruption, so i suppose that's why i've never had an issue. :)

Thanks!
 

Users who are viewing this thread

Back
Top Bottom