> Does anyone know why this happens and how it might be solved.
One thing to check - when you get a user reporting this issue, check to
see if there is an equivalent locking file, ie, ldb extension, on the
server share. IOW, if your mdb is MyProject.mdb, when someone has it
open, there should be a MyProject.ldb.
Check for this. The error you are reporting sounds as if when a user
opens the mdb, the locking file is not being created.

Signature
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Be Careful, Big Bird!" - Ditto "TIM-MAY!!" - Me
DeanL - 01 Feb 2007 20:54 GMT
On Feb 1, 11:22 am, Tim Marshall
<TIM...@PurplePandaChasers.Moertherium> wrote:
> > Does anyone know why this happens and how it might be solved.
>
[quoted text clipped - 10 lines]
> /#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
> /^^ "Be Careful, Big Bird!" - Ditto "TIM-MAY!!" - Me
Hi Tim,
Thanks for that but the locking file is present for the people who get
into the db without a problem, for the other people the locking file
isn't being created because the db doesn't even get as far as opening.
Dean.