Question Access database with different filename extention and ldb files (1 Viewer)

BiigJiim

Registered User.
Local time
Today, 10:20
Joined
Jun 7, 2012
Messages
114
Hi,

I have a client who is running a Front End/Back End Access 2007 database where the back end has a non-standard filename extension (i.e. not mdb, mde, accdb, accde etc.) The extension is not associated with MS Access on his system. (Long story as to why, and its not important here, but he does not want his employees to be able to simply locate the back end database.)

All works fine, except for the fact that in the back end folder, along with the usual filename.ldb, multiple copies of the ldb record locking file keep appearing, with the date and time appended to the filename in the format Filename-YYYY-MM-DD-HH-MM-SS.ldb. These do not get deleted when users log out.

Does anyone know what might cause this? Is it related to having the non-standard filename extension, or another issue entirely?

Thanks for reading, and for any assistance anyone can provide,

Jim
 

The_Doc_Man

Immoderate Moderator
Staff member
Local time
Today, 05:20
Joined
Feb 28, 2001
Messages
26,996
First question is whether the users have correct access to that folder. They SHOULD have the Windows "MODIFY" class of access, which includes low-level permissions for Traverse, List/Read, Read Attributes, Create/Write, Write Attributes, Delete, and (maybe) Read permissions. They don't need Change Permissions, Take Ownership, or Full Control. To be consistent with suggested Microsoft (and other) preferred rules on how to access a file, they should all be members of a particular domain group and the permissions would associated with the group. But not everybody does that.

If they don't have Delete, what you describe might be happening because they can't delete the file. This might actually be detrimental to proper locking synchronization because in that case, their locks aren't visible to each other. You could look at the detailed permissions on the file to see if they all have the same ownership.

This is a short-sighted viewpoint as well. Windows file-type associations are important for various reasons having to do with registry behavior. Further, Access will remember the several most recent files it opened if you open Access directly without a target. Windows will ALSO remember the most recently opened files. Therefore, anyone with knowledge of the registry would be able to find the file in a heartbeat.

The "long story" truly isn't important here for us, you are right about that. But it is important for the client to understand that "security through obscurity" is equivalent to "no security at all" for anyone who is determined to see that file.
 

Users who are viewing this thread

Top Bottom