Locking file on Back End of Database

[Tonytlc]

I have a split database with the BE on the server and the FE on individual
computers. All users have full permissions to the folder on the server
containing the BE. My problem is that when a user accesses the tables on the
BE Access is generating a locking file and keeping everyone else out. The
expected locking file is created for the front end on the loocal machine but
I do not uderstand why one is being created on the BE. I have tried all
variations of setting for the Default Record Locking and the default open
option is set to Shared. I have spent weeks on creating this database and now
only one person can use it at a time which makes it virtually useless. Has
anyone any ideas please. I am getting desperate now and my boss is beginning
to ask some very awkward questions.
Tony

 

[Ken Snell [MVP]]

A locking file (.ldb) for the backend database is normal behavior for a
split FE/BE setup. The fact that the .ldb file is created indicates that the
"user" is not gaining exclusive access to the backend file, as that .ldb
file is how ACCESS trackes the users accessing the BE file.

Did you set the Shared option on the BE file? What message are other users
getting when the BE file is "locked"? Is this behavior noticed only when one
specific user is accessing the BE? or when any user acesses the BE?

 

[Douglas J. Steele]

The locking file is always in the same folder as the database. In reality,
you're have two locking files: one for the front-end and one for the
back-end. Since the point of the locking file is to handle multiuse of the
data, it would make no sense if the locking file for the back-end wasn't
shared!

Are you sure that your users all have full permissions on the folder where
the back-end is? The symptom you're describing isn't consistent with that. I
have heard of cases where users may have permissions on the folder, but do
not have permission to update files created by other users (which is
required)