Question Maintenace Issue

[OldManRiver]

All,

I posted my thread about the DB locking up:

http://www.access-programmers.co.uk/forums/showthread.php?t=180381

This has now left me with a hanging open session in the BE file, which says it is my DEV machine, but soft and hard reboots have not cleared it.

I need to run weekly maintenace, with "Compact & Repair" but am denied, because it say the BE is locked.

I know there is a way to FORCE off the BE file, but can not find it in the MICKEY soft HOWTOs, so need some help on finding that.

I tried to delete the .ldb file for the BE but get the "file in use". I also tried changing from shared to exclusive for the db, but nothing is working.

Thanks!

OMR

 

[boblarson]

1. Make sure everyone is out of the backend.

2. Delete the ldb file (if you can't make sure you and everyone else has delete permissions on that folder as you need to have them).

3. If you still can't delete the ldb file, get your network admin to delete it. I ran into the situation once where we had Novell as the OS on the server and it just would not release an ldb file when things had gone wonky, so the admin had to use a special kill command to get it out.

 

[OldManRiver]

1. Make sure everyone is out of the backend.

2. Delete the ldb file (if you can't make sure you and everyone else has delete permissions on that folder as you need to have them).

3. If you still can't delete the ldb file, get your network admin to delete it. I ran into the situation once where we had Novell as the OS on the server and it just would not release an ldb file when things had gone wonky, so the admin had to use a special kill command to get it out.

B,

I had already done this and it kept telling me it was my DEV machine locking the file. When I turned off the DEV machine was still getting the same answer; so obviously it is something else. I may have to schedule a server re-start, over a week-end with the Sys-Admin.

Thanks!

OMR

 

[boblarson]

B,

I had already done this and it kept telling me it was my DEV machine locking the file. When I turned off the DEV machine was still getting the same answer; so obviously it is something else. I may have to schedule a server re-start, over a week-end with the Sys-Admin.

Thanks!

OMR

Yes, it could be saying the Dev machine was locking it even if it wasn't because the ldb file for some reason has become locked itself and can't update, can't close, etc. Like I said, I have experienced this before but on a server running Novell software as its Operating System. Good luck with getting it deleted