Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error 3050 Could not lock file 1

Status
Not open for further replies.

CharlieT302

Instructor
Mar 17, 2005
406
US
Hi Everyone,

I have never experienced this error before. I have a small database installed on a server. When I try to link to it from a workstation, I receive this error. The help screen said the operating system wouldn't open the ldb file in the same directory as the database, but there is no choice but to do so.

The operating systems are all Windows Vista with one Windows 7. It is a workgroup setup; one computer acting as the file server where the database is installed.

THe folder storing the file grants all permissions to the users, however the Full Permissions box is not checked, but all other options are (read, write, execute, etc).

Any ideas? Anyone else experienced this before?

Thanks
 
I have that done. Actually everthing except: Change Permissions and Take Ownership are checked on.

I keep getting the Could Not Lock File message.

FYI: This happens whether I attempt to open the file from a shortcut link or from within Access using the File open command.

Any other ideas will be much appreciated.

 
CharlieT302,
Answer this specfic question:
Can every user create and delete files in the network folder. Confirm this be creating and deleting a text file in the folder.


Duane
Hook'D on Access
MS Access MVP
 
Good thought. Yes, I can create and delete a file in the network folder from the workstations.

To follow up:
1.) I went ahead and placed full permissions on the folder for the group account
2.) I went to the parent folder and added modify and write permissions.
3.) I did forget to add Open Run permissions to the two Access accounts (we are using User Level Security), but have since corrected that issue. Security accounts work as intended on a stand alone machine.

This is frustrating.
 
One more thing. I made sure the Open Exclusive option is turned off.
 
Just a Follow Up:

I have the problem solved and wanted to share the solution in case others find themselves in the same situation.

As to boblarson's question; the operating system on the server is Windows Vista (workgroup; not domain).

I split the database into a front end/back end setup and put the front end on each workstation's C: drive with a shortcut link on the desktop (to allow for user logins). This allowed the database to open.

However, it was read-only. Upon further investigating I found that while the NTFS permissions were set to Full permissions on the database folder, the Share permissions were not. Once Full share permissions were set, the database was again Read/Write.

My guess is that setting the Share permission alone may have solved the problem without a front end, but haven't checked yet. Although, I prefer a front end anyway.

Thanks for everyone's interest and input.

 
Thanks for the update and I'll add that piece to my list of things to suggest to look for when someone else has that problem.

Bob Larson
FORMER Microsoft Access MVP (2008-2009, 2009-2010)
Free Tutorials/Samples/Tools:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top