I'm trying to figure out how to solve an Access problem for a company I do part time work for. I can dial in and check the DB in question but I'm not there during the day when the users have this problem. The network support guy emailed me the following comment:
We have an access file named log-ins2 located on our Windows 2K server. The problem people are having with it is that 2 people have full access to it and others have read only. If one of the full access people open it before the read only people do they get a 'can't lock the file' error.
The privs of the people to the folder have been checked and seem identical. I looked in the DB and it's pretty much wide open, in fact some users enter data directly into tables. Also, if a "readonly" user gets to open the DB first there doesn't seem to be any problems.
I'm thinking that perhaps the full access users are creating a log file with tighter privs on it? But I don't know how that can happen. There's not really any code running in the background that would do this that I'm aware of.
I did note that at least some of the people are still running Access 2000 and not Access 2007. The support guy who contacted me said that when he opened the DB today on a Access 2K machine, he did not see the security messages that allowed the user to enable macros and such. I do get those messages when I opened it on my PC but I have Access2007.
The DB has an MDB extension and indeed when I open it up Access tells me it is in Access 2000 format.