What are ldb file?

[Guest_imported]

Can someone please tell me what ldb files are in access?

Thanks

 

[LittleSmudge]

What it is ? or what it's for ?

When Access opens a .mdb file a .ldb file is created of the same name in the same folder. This file contains information about WHO the person is ( or people are ) that's logged in to the .mdb

When the last person loggs out of the database then Access SHOULD delete the .ldb file ( housekeeping ).

Occasionally ( eg. if you have a 'Blue Screen of Death' event while you have an access database open ) the ldb does not vanish. From Windows Explorer you can just simply delete it. ( If it won't delete but reports access violation issues then someone else is logged into the system )


'ope-that-'elps.

G LS

 

[Guest_imported]

Thanks, that explains.
See one of my co-workers went on vacation last week. He is the only access programmer in the shop. I can use access but I am not a pro at it.

Corp [NYC office] has requested a change, and since I an the only one who is familiar with access they asked me. The change requires to modify a paragraph in a pdf letter he is generating. I have tryed to open the database with no luck, everytime i want to open the database I get: "The database you are trying to open or convert is in use, or you do not have permission to open it exclusively".

I tryed deleting the file but it did not work. I have been given full right to the server were the db is.

Is there any other way of opening it?

Thanks in advance.

 

[pjdavey]

Have you tried opening it without the "exclusive" box
ticked in the open dialogue ?

 

[Redcatcher]

Here's my guess. It sounds to me like your co-worker might have left the file open at his PC when he went on vacation. Is his PC turned on? Or perhaps someone else who uses that file with a different level of access than yours might have it open.

 

[Francescina]

Here is an article from the ACCESS ONLINE ENCYCLOPEDIA (

http://www.unsoftwareag.com).

Maybe it helps you!


Article Code: N1

N1: What is the LDB file good for?
For every database opened for shared use, an .ldb file is created to store computer and security names and to place extended byte range locks. The .ldb file always has the same name and is located in the same folder as the opened database (.mdb or .mde).

When the last user closes a shared database, the .ldb file is automatically deleted. The only exception is if a user does not have delete rights for the folder, when the database is marked as corrupted or if ACCESS is not properly closed.
In these cases the .ldb file is not deleted because it contains information about who was using the database at the time the database was marked as corrupted. If you want to use database in a multi use environment then the .mdb file should be located in a folder where users have read, write, create and delete permissions. Even if you want users to have different file permissions (for example, some read-only and some read-write), all users sharing a database must have read, write, and create permissions to the folder. You can, however, assign read-only permissions to the .mdb file for individual users while still allowing full permissions to the folder.

If a user opens a database with exclusive access (by selecting the Exclusive check box in the Open dialog box), record locking is not used and ACCESS does not create an .ldb file. In this case the user needs only read and write permissions to the folder.

For each user opening a shared database, ACCESS writes an entry in the database's .ldb file. The size of each .ldb entry is 64 bytes. The first 32 bytes contain the computer name . The second 32 bytes contains the ACCESS login name. The maximum number of concurrent users is 255; therefore, the .ldb file size is never larger than 16 kilobytes.

When a user closes a shared database, his entry is not removed from the .ldb file. However, it may be overwritten when another user opens the database. This means that you cannot use the .ldb file to determine the current users of a database.

The ldb file information is used to prevent users from writing data to pages that other users have locked and to determine who has locked. If the Jet database engine detects a lock conflict with , it reads the .ldb file to get the computer and security name of the user who has the file or record locked.

In most lock conflict situations, ACCESS generates a Write conflict error message that allows the user to save the record, copy it to the Clipboard, or cancel the changes. In some circumstances, however, you receive the following error message:


Couldn't lock table TABLE NAME currently in use by user
USER NAME on computer COMPUTER NAME.



If you receive this message while you are the only user, then close the database and delete the orphan LDB-file.

The state of the information in the .ldb file has no influence on the state of the database. If an .ldb file becomes corrupted, everything in the database should still work correctly. However, you may see garbled text instead of user names in any lock conflict messages