GregSmith at starband.net
GregSmith at starband.net
Wed Feb 2 09:20:23 CST 2005
I've always had and ldb (small "L") file present when someone logs into a database...and for a split db, there is one for the FE, one for the BE and one for the security file...but they're all ldb, not md"x" files. The security file, SecFile.mdw would have a corresponding SecFile.ldb associated with it when someone logs in. Same with the FE and BE files-a corresponding *.ldb file. I can't find any reference anywhere to mdl (small "L") on M$ or Google... If you login "Exclusively" to a db, then this ldb file does not open, letting Access know that nobody else can login because the file is 'locked' by an exclusive user. Greg > This is probably a mdl file (l not 1). > A mdl file is always present when somebody has opened the database file, > in this case the security file. > In this file all locks are kepded and is needed for Access to operate. > > This does not cause any lockouts for users unless some bad programming > or other (security?) issues. > > > Erwin > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, > Karen > Sent: Tuesday, February 01, 2005 5:26 PM > To: accessd at databaseadvisors.com > Subject: [AccessD] What is this .md1 That Is Locking My Security File? > > Now Access is being rude to me. I recently moved the security file that > controls my database from each person's own hard drive to a centralized > location on the network. Every couple of days, the security file named > rb.mdw has a friend, rb.md1, locking out most of the users. Does anyone > know what this is and how to prevent it? Thanks. > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com