M
mikej711
I run a part-time business customizing Access databases. All my
databases are split so that I can maintain duplicates which are
structurally identical to my clients but full of testing data.
One of my clients running an 2002 database is having a strange problem
with user-level security. After a year of use, their first read-only
user is introduced. I had already written a read-only group into the
group and anticipated no problem, but the user can’t log on. The funny
part is, I entered the same account into my test-copy and it works
fine.
If the user is given editing rights, she can see the switchboard on
the client database but not read-only, even though the switchboard
does no editing.
Any suggestions you can offer would be greatly appreciated.
databases are split so that I can maintain duplicates which are
structurally identical to my clients but full of testing data.
One of my clients running an 2002 database is having a strange problem
with user-level security. After a year of use, their first read-only
user is introduced. I had already written a read-only group into the
group and anticipated no problem, but the user can’t log on. The funny
part is, I entered the same account into my test-copy and it works
fine.
If the user is given editing rights, she can see the switchboard on
the client database but not read-only, even though the switchboard
does no editing.
Any suggestions you can offer would be greatly appreciated.