vb123.com

Garry Robinson's Popular MS Access, Office and VB Resource Site

 

Home  Contact Us
Order our Software

RSS & Newsletter  
Join our XML/RSS Newsfeed or sign up for our informative newsletter on Office Automation, Access and VB topics
Read More

Get Good Help
If you need help with a database, our Professionals could be the answer
Read More

  Is Your Database Corrupt ?
If you have a corrupt database, Try our Access Recovery service

The Workbench  Find out who has your database open, start the correct version of Access, easy compacting and backups, change startup options, mde compile,  shutdown database Read and Download

The Toolshed 
Searchable help file comprising of all the information at vb123.com plus hidden downloads etc. Read More



The Toolbox

Libraries of software that we regularly import into our projects. Enhances the Toolshed More..


Upsize to SQL 
Upsize to SQL Server 2005 or 2008 or improve the performance of your Access to SQL Server application
Read More


DryToast New
Backup and query your BaseCamp
® projects
Read More


Datamining/Graphs

Explore your data with this versatile graphing and data mining shareware tool.  Read More

Garry's Blog
Find out a few other things that Garry has been writing about Microsoft Access. Read more

About The Editor Garry Robinson writes for a number of popular computer magazines, is now a book author and has worked on 100+ Access databases. He is based in Sydney, Australia
Contact Us ...

Search ...

or try our new Expression Web
 vb123.com.au
 

 

Next Tip  The LDB File
This is a sample from the Microsoft Access Protection book by Garry Robinson

Whenever you open an Access database, Access will open a file with the same name as the database and an extension of .LDB. This file type is known as a locking information file. For example, if you open Northwind.mdb in the samples directory of your Access/Office installation, a file called Northwind.ldb will be generated. This new file keeps track of users and the locking status of every object that requires some form of locking in the database. When all users have exited the database by closing it in an orderly manner, Access will close the .LDB file and delete it.

The internals of the .LDB file are important for database sharing. The file stores the computer name and workgroup file security names of those users who are currently logged on to the database (with the occasional exception). It also stores the objects that that user has open or locked in a special and flexible part of the workgroup file.

NOTE Access needs to delete the .LDB file when it closes so that databases work properly and to allow for performance improvements when determining which other users have locks. Therefore, everyone who uses the folder in which the database is stored will need write and delete permissions for files in that folder. You will find out more about Windows folder permissions in Chapter 12.

To find out more about the .LDB format, read the white paper Understanding Microsoft Jet Locking (LDB Files) by Kevin Collins. This paper is included in the LDBView download files, or you can find a link to it in the “Further Reading” section with other .LDB pages at the end of this chapter.

Find Out More

This topic and more are discussed at length in Chapter 6 of Garry's Book on Access Protection and Security
Read More
You should also read more on the ldb file in the help provided with the Access Workbench

Other Pages At VB123.com That May Be Of Interest

Microsoft Access Passwords, Workgroups and ADO
Take Advantage Of The Class Module Features Of Your Access Forms

Click on the following button Next Tip to jump to the next page in the protection samples loop.

 

Links >>>  Home | Search | Workbench | Orders | Newsletter | Access Security | Access professionals