Could not lock file. (Error 3050) = Please help!

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DMI - 11 Jul 2006 15:01 GMT

Gentlemen - I have a problem with one of our databases. I would like to
have one person able to modify the database and every body else should only
have read access to the database. The problem is when the person who has
full access is in the database nobody is able to view the database at all.
The error we are getting is "Could not lock file". This has to do with the
inability to create the ldb file in the directory where the database is. I
would like for everybody to have read access and able to view the data in the
database.

How do I do this?

Please advise and thank you for your help!
Please advise and thank you for your help!

Reply to this Message

Tony Toews - 13 Jul 2006 03:38 GMT

>Gentlemen - I have a problem with one of our databases. I would like to
>have one person able to modify the database and every body else should only
[quoted text clipped - 4 lines]
>would like for everybody to have read access and able to view the data in the
>database.

Unfortunately there is currently no way to do what you are looking
for.

One option might be to create another read only directory and once a
day or other convenient interval copy the updated backend to that
directory. The obvious downside is that the other folks will be
looking at a day old copy of the data.

Tony

Signature

Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Reply to this Message

css mv it - 20 Jul 2006 22:22 GMT

I had something like that working in a peer-to-peer environment, but since
moving to Server 2003 and terminal services I'm starting to get this message.
If the read-only user(s) sign on first, they can get in. It's only AFTER
the updater opens the database that subsequent readonly users get the "lock"
error. If you don't have too many users and they are friendly, you can ask
them to work around the problem by having the updater close the database
every time a readonly user wants to get in.

At least until we figure out what to do next.

> Gentlemen - I have a problem with one of our databases. I would like to
> have one person able to modify the database and every body else should only
[quoted text clipped - 9 lines]
> Please advise and thank you for your help!
> Please advise and thank you for your help!

Reply to this Message