One user getting read-only error

[brigitte]

I have installed the front end for my database on several machines
(the front end is an mde), which links to a back end on a network
drive all my users have access to. To prevent mapping errors, the
links are done with the full network path (no shortcut letters).

The setup has worked on all machines, except one. This user keeps
getting errors when he attempts to write to the tables. By copying the
original front end mdb on his machine and running that instead of the
mde, I've been able to see that the error is due to the system
thinking he only has read-only access to the back-end.

I've checked the security on the drive and folder where the back end
is located, and all the groups who have access to it at all have read
and write access. There appears to be nobody who has only read-only
access to this file.

I've checked the macro security setting for the user and it is set to
low, like most of my other users.

I've logged in as myself on this user's machine and the front end
works for my account.

I can't figure out why his system thinks he only has read-only access
to the back-end. Access also said the front end was read-only when I
opened the mdb (which it shouldn't be, but all the tables are linked
from the back end and the front end doesn't need to be written to by
the user, so other than for the possible correlation, this doesn't
concern me as much).

Is there a setting somewhere in Access that automatically makes Access
treat anything as read-only? I'm completely stumped.

Thanks for your help,

Brigitte

[Bob Quintal]

br******@mun.ca wrote in
news:7ba0c43a-1471-44a1-aa7d-a0577f83dc86
@f47g2000hsd.googlegroups.co
m:

I have installed the front end for my database on several machines
(the front end is an mde), which links to a back end on a network
drive all my users have access to. To prevent mapping errors, the
links are done with the full network path (no shortcut letters).

The setup has worked on all machines, except one. This user keeps
getting errors when he attempts to write to the tables. By copying
the original front end mdb on his machine and running that instead
of the mde, I've been able to see that the error is due to the
system thinking he only has read-only access to the back-end.

I've checked the security on the drive and folder where the back
end is located, and all the groups who have access to it at all
have read and write access. There appears to be nobody who has
only read-only access to this file.

I've checked the macro security setting for the user and it is set
to low, like most of my other users.

I've logged in as myself on this user's machine and the front end
works for my account.

I can't figure out why his system thinks he only has read-only
access to the back-end. Access also said the front end was
read-only when I opened the mdb (which it shouldn't be, but all
the tables are linked from the back end and the front end doesn't
need to be written to by the user, so other than for the possible
correlation, this doesn't concern me as much).

Is there a setting somewhere in Access that automatically makes
Access treat anything as read-only? I'm completely stumped.

Thanks for your help,

Brigitte

No, the problem is most likely one of the following:
1) user does not have write permission in the be directory,
2) user does not have modify permission in the be directory,
3) user does not have sufficient rights to open .ldb (Access recored
locking file) which has been created by another user.
--
Bob Quintal

PA is y I've altered my email address.

--
Posted via a free Usenet account from http://www.teranews.com

[brigitte]

Thank you for your reply.

I only have three groups who have access to this particular drive, and
all three have read and write access. I didn't think of copying a file
while logged in as the user, but I did open an excel file to see if I
was getting a "read-only" message, and I didn't.

Because of that, I just don't see how it could be a permission
problem, but I'm having him log on from a different machine to see
whether the problem is still there or not: this should determine
whether the problem is his permissions or something strange about his
computer/Office installation/who knows what else.

Thanks again!

Brigitte