Corrupt LDB

[TKnight]

Hi, I have a networked DB and I can't update the FE because the LDB file is locked. It says there are about 8 users in the DB which I know isn't true (I keep a table of current users and I prevented any new people from logging on before I went home last night)

I've never had this happen before? Does anyone know how I can fix it and kill the connections/Delete the .ldb?

I'm sure I caused the problem cause I've just put a few weeks development into the live system but i'm not sure why. I know if I have left recordsets open this can keep the connection but are there other reasons why this may be happening?

Thanks, Tom

 

[ghudson]

All of the computer names stored in the .ldb file must be rebooted to disconnect their link to the db file. One of those computers still has a connection [lock] on the db which is why you can not delete the .ldb file.

 

[KenHigg]

As an alternate solution, you may need to get the network admin to force users out.

 

[TKnight]

Well in theory staff are supposed to shutdown before they go home which should have reset all the connections last night. I'm sure all 8 didn't leave their PC's on overnight and as they left they should have dissapeared out of the .ldb shouldn't they? But I halted all new connections before I left and the same 8 were still in the .ldb first thing this morning.

It's a bummer cause this DB doesn't require proper security so everyone is in the LDB as "admin" and the machines are numbered rather than named. We have 2000+ machines in the office which is why I log the users on with a simple login script and store them in case such a situation arises but it's no good to me now because the .ldb isn't showing accurate info.

Maybe I can pass the ID's to network admin and get them to implement your solution Ken...

Thanks for your help guys,

Tom