Database Help

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Chris Savedge - 29 Nov 2004 16:00 GMT

I created a daily reporting database about 4 years ago so our customer service department could run a multitude of different reports as they needed to. The database sets out on our server and all of the users have a link to it on their desktops. 99% of the time this database functions very well but every once in awhile the users will get halt messages or a message that says the database is locked. When I go out and look to see who is in the database I notice that the LDB file that is attached to a user says things like 5 locks or 7 locks? First I would like to know if you guys have any suggestions about my set up and also what is the LDB locking situation all about and does it cause problems?

Thanks so much for your time,
Chris

Signature

CHRIS SAVEDGE

Reply to this Message

Amy Vargo - 29 Nov 2004 20:12 GMT

Hi,

My name is Amy Vargo. Thank you for using the Microsoft Access Newsgroups.
Make sure that all users have full control to the folder where your .mdb
file resides and that there is not a leftover .ldb file if all users are
closed out of the database. When you open a database, a .ldb file is
created in the same folder where the .mdb file resides and should
automatically delete itself when you close the file. If a user does not
have correct permissions, the .ldb file might not be able to create or
delete itself, thus causing an error.

For more information, please see the article below.

136128 ACC: Introduction to .ldb Files (95/97)
http://support.microsoft.com/?id=136128

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.

Regards,

Amy Vargo
Microsoft Access Engineer

This posting is provided 'AS IS' with no warranties, and confers no rights.
You assume all risk for your use. ? 2001 Microsoft Corporation. All rights
reserved.

Reply to this Message

Larry Linson - 30 Nov 2004 00:55 GMT

> ... reporting database ... sets out on our
> server and all of the users have a link to it
> on their desktops. 99% of the time this
> database functions very well but every
> once in awhile the users will get halt messages
> or a message that says the database is locked.

It appears from your post that you allow multiple users to log in to the
same front end or monolithic database. That significantly increases the
chance of corruption, and can cause other problems, too. You should split
the database into a front-end (queries, forms, reports, macros, and modules)
and put a copy on each user's machine; link these copies to a common
back-end (tables with data, and relationships) on the server.

There's an introductory presentation on Access in a Multiuser Environment
that I did for my user group that you can download from
http://appdevissues.tripod.com. It will identify topics that I thought
worthwhile to discuss, and a bit more. The best collection of detailed
information and links on the subject of Access in the multiuser environment
is at MVP Tony Toews' site, http://www.granite.ab.ca/accsmstr.htm. You will
also find there Tony's free front-end updater to ease the administration of
multiple copies of the front-end.

Larry Linson
Microsoft Access MVP

Reply to this Message