No, the locking file is always created (unless you open the database as
exclusive and read-only).
Do all the users have the same permissions on the folder where the MDB file
exists? They need at least Change (Read, Write, eXecute and Delete)

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> If I turn off record locking and set db to shared on the front-end and
> back-end, when the users open the front-end should it also open a .ldb
[quoted text clipped - 8 lines]
> updates. Now, I assuming it's my db and I'm lost at what it could be.
> Anyone got any ideas.
Leslie - 28 Mar 2007 20:04 GMT
Thanks for answering Doug...I posted the same question again because I could
not find this one. Anyway, I have talked to our I.T. dept and they say all
the users in question have the same permissions. When the fourth user open
the db, it opens fine but when she goes to add a record, she immediately get
a "Run-time" error.

Signature
Leslie
> No, the locking file is always created (unless you open the database as
> exclusive and read-only).
[quoted text clipped - 14 lines]
> > updates. Now, I assuming it's my db and I'm lost at what it could be.
> > Anyone got any ideas.
Douglas J. Steele - 28 Mar 2007 20:27 GMT
Is your application split into a front-end (containing the queries, forms,
reports, macros and modules), linked to a back-end (containing the tables
and relationships)? Only the back-end should be on the server: each user
should have his/her own copy of the front-end, ideally on his/her hard
drive.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> Thanks for answering Doug...I posted the same question again because I
> could
[quoted text clipped - 28 lines]
>> > updates. Now, I assuming it's my db and I'm lost at what it could be.
>> > Anyone got any ideas.