J
James Strachan
Before I begin, I realise that there is probably no way
round this problem from other posts I have read and
placed on various forums, but I think it is a problem
that Microsoft could and should rectify!
The problem we are having is that one of our users has
created a database which merges data from two folders.
Some users only have read only access to one of these
folders, meaning that if a .ldb file exists (Someone has
the database locked) they are unable to write to the .ldb
file, and are unable to open the database. If the same
users open the database when it is not in use however,
they are able to open it, recieving a 'This document is
read-only' message from Access (because Access tries to
create the .ldb file if it is not there, fails to create
it, so opens the file as read only).
I realise that a possible way around this is to give
everyone write access to the folder, and change the
access rights of all the individual files, but I am
reluctant to do this due to disasters in the past!
Surely if when Access fails to create a .ldb file it
opens the db as read only, it would not be difficult, or
a security issue for it to open the db as read only after
attempting to edit a .ldb file and failing.
Any thoughts?
Cheers, James
round this problem from other posts I have read and
placed on various forums, but I think it is a problem
that Microsoft could and should rectify!
The problem we are having is that one of our users has
created a database which merges data from two folders.
Some users only have read only access to one of these
folders, meaning that if a .ldb file exists (Someone has
the database locked) they are unable to write to the .ldb
file, and are unable to open the database. If the same
users open the database when it is not in use however,
they are able to open it, recieving a 'This document is
read-only' message from Access (because Access tries to
create the .ldb file if it is not there, fails to create
it, so opens the file as read only).
I realise that a possible way around this is to give
everyone write access to the folder, and change the
access rights of all the individual files, but I am
reluctant to do this due to disasters in the past!
Surely if when Access fails to create a .ldb file it
opens the db as read only, it would not be difficult, or
a security issue for it to open the db as read only after
attempting to edit a .ldb file and failing.
Any thoughts?
Cheers, James