You can, however, assign read-only permissions to the.
Even if you want users to have different file privileges (for example, some read-only and some read-write), all users sharing a database must have read, write, and create permissions to the folder. If you plan to share a database, the database file should be located in a folder where users have read, write, create, and delete privileges. Then, the lock file isn't deleted because it contains information about who was using the database at the time the database was marked as corrupted. The only exceptions are when a user doesn't have delete rights or when the database is marked as corrupted. Whenever the last user closes a shared database, the lock file is deleted. For example, if you open (for shared use) the Northwind.accdb sample database in C:\users\\documents\, a file named Northwind.laccdb is automatically created in the same documents folder. The lock file always has the same name as the opened database, and it's located in the same folder as the opened database. Automatic lock file creation and deletionįor every database that's opened for shared use, a ".laccdb" or ".ldb" file is created to store computer and security names and to place extended byte range locks. Both the ".laccdb" and ".ldb" files are commonly referred as lock files. accdb databases and the ".ldb" file is used with ".mdb" databases. The ".laccdb" or ".ldb" file is used to determine which records are locked in a shared database and by whom.
The ".laccdb" or ".ldb" file plays an important role in the multi-user scheme of the Microsoft Access database engine. For more information about this change, read this blog post. Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise.
0 kommentar(er)
