MS Access Multiuser - CAn't delete ldb or compact/repair

Author

CAn't delete ldb or compact/repair

Kevin Witty

2005-04-18, 9:24 am

I have several backends on a remote desktop connection. One of them has an
ldb file which I can't delete. I've used Computer Management to close all
open connections to its mdb file, but I still can't delete the ldb, and can't
compact/repair the mdb.

I've seen this happen once before, and ended up having to copy the mdb with
a new name and then link the front end to that copy. I'd rather not do that.

How do I close this puppy?

Kevin

Michael Cheng [MSFT]

2005-04-19, 3:25 am

Hi Kevin,

From your descriptions, I understood that you are not able to delete *.ldb
file and your access is closed. If I have misunderstood your concern,
please feel free to point it out.

Based on my scope, when network switch does not release the connection with
the server or database, ldb file will not be able to delete. Somebody shun
down the PC direcly may also lead to the behavior. Please perform the steps
below and let me know whether it works for you

1. If you have admin priviledges on the server, you can go to My Computer
-> Manage, and choose Open Files. Then boot whomever is connected and close
the file.

2. I would recommend that you ask your network department for help in
troublshooting this issue. They should be able to help you track down what
is holding a lock on the database.

3. If you don't have a network department then I would try turning all pc's
off, rebooting the server, turn on only 1 pc, try to compact the database,
and if successful bring all other pc's up. If this doesn't resolve your
problem then you will probably need to talk with some networking people
about your issue.

If there is any error message you could find in Dialog box or Error Log,
please feel free to post them here let me know. The following KB provide
another way to monitor this behavior in the future about how to use
Microsoft Visual Basic for Applications to output a list of users who are
logged onto a database

How to determine who is logged on to a database by using Microsoft Jet
UserRoster in Access 2002 or in Access 2003
http://support.microsoft.com/kb/285822

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================
====================
=============

This posting is provided "AS IS" with no warranties, and confers no rights.

Kevin Witty

2005-04-19, 9:24 am

Thanks, Michael. I'll try rebooting the server and trying to compact with
only one PC up. I've tried pretty much everything else.

Kevin

"Michael Cheng [MSFT]" wrote:

> Hi Kevin,
>
> From your descriptions, I understood that you are not able to delete *.ldb
> file and your access is closed. If I have misunderstood your concern,
> please feel free to point it out.
>
> Based on my scope, when network switch does not release the connection with
> the server or database, ldb file will not be able to delete. Somebody shun
> down the PC direcly may also lead to the behavior. Please perform the steps
> below and let me know whether it works for you
>
> 1. If you have admin priviledges on the server, you can go to My Computer
> -> Manage, and choose Open Files. Then boot whomever is connected and close
> the file.
>
> 2. I would recommend that you ask your network department for help in
> troublshooting this issue. They should be able to help you track down what
> is holding a lock on the database.
>
> 3. If you don't have a network department then I would try turning all pc's
> off, rebooting the server, turn on only 1 pc, try to compact the database,
> and if successful bring all other pc's up. If this doesn't resolve your
> problem then you will probably need to talk with some networking people
> about your issue.
>
> If there is any error message you could find in Dialog box or Error Log,
> please feel free to post them here let me know. The following KB provide
> another way to monitor this behavior in the future about how to use
> Microsoft Visual Basic for Applications to output a list of users who are
> logged onto a database
>
> How to determine who is logged on to a database by using Microsoft Jet
> UserRoster in Access 2002 or in Access 2003
> http://support.microsoft.com/kb/285822
>
> Sincerely yours,
>
> Michael Cheng
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================
====================
=============
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Michael Cheng [MSFT]

2005-04-26, 3:26 am

Hi, Kevin

I wanted to post a quick note to see if you would like additional
assistance or information regarding this particular issue. We appreciate
your patience and look forward to hearing from you!

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================
====================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/

If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
====================
====================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Kevin Witty

2005-04-26, 3:26 am

Thanks, Michael, Yes, we did reboot the server and compact and repair the mdb
from the first PC up, and it did work.

I really appreciate the help I've gotten here. I have to admit, though,
that after 30 years in this business, I've had so many problems in the past 2
weeks with screwups due to bad MS code that I'm seriously considering getting
the hell out, which would be too bad, because I really love what I do. I'm
just not sure I can take much more dealing with the crap MS has given us.
Too much, too fast, too bad, too much thought, too little understanding.

Kevin

"Michael Cheng [MSFT]" wrote:

> Hi, Kevin
>
> I wanted to post a quick note to see if you would like additional
> assistance or information regarding this particular issue. We appreciate
> your patience and look forward to hearing from you!
>
>
> Sincerely yours,
>
> Michael Cheng
> Microsoft Online Partner Support
>

Yan-Hong Huang[MSFT]

2005-04-26, 3:26 am

Hello Kevin,

This is Yanhong, tech lead of MSDN managed newsgroup support team. Michael
Cheng reported your concern to me just now.

First, thanks very much for your feedback. I quite understand your feeling
here due to the inconvenience that it brought to you and your team.
Sometimes we get unexpected error and are not sure of the root cause. It
may take much time for you to troubleshoot and resolve it.

That is one of the reasons of why we open managed newsgroup support. Here
we could discuss issues with all people who are using Microsoft product and
technology. We'd like to set up one environment for smooth communication
between our customers and our product team. We are collecting feedback here
and reporting it to our product team. I appreciate your feedback so much,
and it is this kind of feedback that let us know what things you are trying
to do.

If you have any more concerns or there is any new question, please feel
free to post here. We are here to support you at your convenience.

Thanks again for your understanding.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
-http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.as
p&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Sponsored Links