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

John,

<<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. >>

  You would think so, but Jet workgroup security is always "on" and is
always working whether you realize it or not.   When you open any Jet DB, a
corresponding workgroup file is opened as well.  That's true for A2007 and
up to which supposedly had workgroup security "stripped out".

  Microsoft did not remove it.  All they did was remove the ACL's in the DB
if you had any and gave you no way to add new ones back in.  So what they
did is simply disabled it, which is what you have by default when you "don't
use workgroup security" in earlier versions.

  But with not using workgroup security, and with 2007 and up (the workgroup
file name is SYSTEM.MDW BTW and is created on the fly - it suffixed too if
you run through an install and there's already one there - i.e.
SYSTEM1.MDW), the chances of having two DB's in the same directory with the
same name are remote.

<<So, for my own practices, I ALWAYS create a FE/BE scenario...I find it the
most stable and consistant. >>

 And that's definitely a best practice and makes sense in so many ways, it's
something that should be done automatically right from the start.   But over
the years, the sharing of a FE has gone from "it's a bad idea" to "you can't
do that".   You can, and in many cases, it works perfectly fine.   There are
cases where it doesn't work so well, but usually that's more the fault of
the network then it is of Access since A2000.  When the change was made that
you could not make design changes without exclusive access (the underlying
reason being that the VBA project is now saved as a single chunk rather than
a bunch of pieces), shared FE's picked up a lot of stability. 

  So it's not so much of a no-no as it was in the early days, but it's still
not a hot idea.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Clark
Sent: Wednesday, January 15, 2014 07:54 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [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.