"Can't lock file" error on .mde for some people 1

[FranS37]

I have a .mde file sitting in a network folder. It's a front end application with links to both Access (.mdb) and SQL back end data. Both front end and back end Access databases are set to shareable.

It's working fine for for some people, but there are certain users who get a "Can't lock file " error when they try to open it. This only happens to them if someone else already has the .mde open.

Any ideas?

 

[MakeItSo]

The meaning of using frontend-backend structure is that the frontend-db is stored on the local harddrive of the user.

You don't need to "share" a frontend. Just have each user use a copy of the frontend, stored locally. That should solve the problem.

Regards,
MakeitSo

Andreas Galambos
EDP / Technical Support Specialist
(andreas.galambos@bowneglobal.de)
HP:

http://www.andygalambos.de

 

[FranS37]

I agree. But putting the .mde on the server makes it easier to distribute updates. And is there any reason why it shouldn't work?

 

[MakeItSo]

An MDE file has the advantage that you cannot open anything in design view - which could lock the form for others.

But in any case, you could get a deadlock if two users try to open anything at the same time. No sharing can prevent this. Only option then is to re-try after a moment.

There have been several threads about how to regularly update locally stored frontends. You could do this e.g. via a batch-file.

I have solved this by always using the same folders.
My backends are stored on one shared folder, all users have mapped it as drive "X". Frontend is always stored in a folder, say "C:\DB\". I have written a little install.bat, so on Updates, i inform all users per mail, so they execute the update batch:

echo off
c:
cd c:md db
cd db
copy X:\db\Client\frontend.mde
copy X:\MKBase\Client\frontend.lnk
exit

They only have to send the link to desktop once. Since only the mde is altered, they always have latest version locally, no need to change the link...

Would that be a solution?

Andreas Galambos
EDP / Technical Support Specialist
(andreas.galambos@bowneglobal.de)
HP:

http://www.andygalambos.de

 

[FranS37]

Yes, I agree that could be a solution and thank you for the information you provided. But I don't understand Your statement:

"An MDE file has the advantage that you cannot open anything in design view - which could lock the form for others.

But in any case, you could get a deadlock if two users try to open anything at the same time. No sharing can prevent this. Only option then is to re-try after a moment."

No one is trying to open anything in design view, and waiting a few minutes doesn't make a difference. And by nature, Access is meant to be multi-user. And I've used this method many times with .mdb and .mde files.

There must be something else going on.

 

[MakeItSo]

Hmm: waiting a few minutes doesn't make a difference

Of course, no one is trying to open anything in design view. It's just not possible with an MDE. That's what I was trying to say.

But that one statement in italics makes me think that the whole problem is simply caused by the net-share permissions of the affected users. Do they have write permission? If not, Access cannot create a lock file for them.

Talk to your network support people, they should give them rights for this folder.

 

[FranS37]

I believe the users affected have read-only rights to those folders. I'm told by the network people that this works with other Access users. But your point about the lock file makes sense of course. I'll check that out.

Thanks,

Fran