.LDB Question

[KenHigg]

How is it that sometimes when a user quits a db, they're not removed from the .ldb. What mechanisim is supposed to remove them that is failing? Is there some trick code to make sure the .lbd is updated and current?

 

[Pat Hartman]

I've only seen this happen when the db is not properly closed as happens when network connections are lost or the system freezes and must be rebooted.

The .ldb file may be left on the server even when the last user properly logs out but does not have sufficent network permissions to delete the .ldb file. In that case, the user is logged out so you should not see him as active in the .ldb but the .ldb file cannot be deleted.

 

[KenHigg]

Hum...

I could go right now and look a the .ldb and it may show 10 users, all of but say two are not using the db. It's always that way. But, funny thing is, if those two users log out, the .ldb goes away.

I'm kind of thinking it must be a network permission issue...(?)

 

[ghudson]

All users are not removed from the .ldb file as long as somebody is still in it. The .ldb will show everybody what has opened the db but I also have noticed that it does not remove each user from the .ldb file as long as somebody still has it open. The .ldb file will disapear when the last user closes the db [unless somebody did not exit the db correctly (lost network connection, hardware failure, they Ctrl+Alt+Deleted it or the last user does not have delete permissions to the directory)].

 

[KenHigg]

Hum... Something is removing them. If I go back and look, say in a week, everyone that has had the db open since the last time I checked will not be listed. And there will always (24/7) be two or more people in the db so it's never going to be where nobody is in it...

 

[ghudson]

The users are usually [but not always] removed from the .ldb file when the user closes the db [yet somebody else still has it open]. Another reason why reading [opening] the .ldb file is not an accurate way to determine who is in the db.

Also, how to you compact or update the design of the db if there is always somebody in it?

This might interest you...
How to determine who is logged on to a database by using Microsoft Jet UserRoster in Access 2002 or in Access 2003
I have never used it but I would like to see your comments if you do try it.

 

[KenHigg]

Also, how to you compact or update the design of the db if there is always somebody in it?

That's part of the problem. When I do have to ask everyone to get out, the list takes me on a wild goose chase. Next time I'll do an automated routine with a message to the users thing that forces everyone out.

This might interest you...
How to determine who is logged on to a database by using Microsoft Jet UserRoster in Access 2002 or in Access 2003

Thanks, I'll give it a whirl next week...

I have never used it but I would like to see your comments if you do try it.

Refreshing to see that not all of the forums more experienced users have such dogmatic responses...

 

[ghudson]

Refreshing to see that not all of the forums more experienced users have such dogmatic responses...

I only chastise the lazy ones.

 

[KenHigg]

I only chastise the lazy ones.

I'll try to stay on my toes and hopefully learn something

 

[WindSailor]

I'll try to stay on my toes and hopefully learn something

Funny... When I try that, I usually fall foward for some odd reason... must be an age thing...