[AccessD] Back-End DB is locking...WHY?!

Anytime any JET database is opened, a locking file is created.  If a LDB file cannot be created because of permissions, the DB is opened exclusive.
***** I did not know this...thanks for the info. I did find it to be a rights issue, but knowing the "exclusive" open would have helped, because I did see a message regarding this pop up once. 

One thing to watch out for; DB's with the same base name, but a different extension.  Ie.

myApp.MDW
myApp.MDB

When you go to open myApp.MDB, with myApp.MDW being the workgroup file (which is also a JET database), both get the same LDB file name; myApp.LDB and all kinds of weird stuff will happen.
 
***** Yeah, I'm pretty good about altering the names, if only a little bit. And, I absolutely hate Access security, so I avoid it like the plague. It is pretty much unnecessary in a network environment...in my opinion...so that's not a tough one. 

So check for that first. Then with everyone out, delete any LDB files. Make sure the DB open mode is shared.
 
And by the way, you can share a DB fine, it's just not recommended and not the most efficent for a number of reasons.
 
***** I've heard so many opposing views on this in the past 14+ years...BUT...from my own experience, sometimes it just will not work, and I don't get how it sometimes will, and then suddenly stop. So, for my own practices, I ALWAYS create a FE/BE scenario...I find it the most stable and consistant. 

Jim. 
***** Thanks for the help Jim
 
J Clark

Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. 
IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. 
Thank you for your cooperation.