P
PtrNrs
Note: P.S.: In this post, I have dealt with queries but I believe the
behaviour can be generalised to tables, forms & reports as well.
I have a secured Access 2000 database and wish to populate a combo box
with queries for which the current user has read permission or better.
I have done this before with success with an old database (Access 2K)
but my new database returns (for instance) error 3112 "record(s) cannot
be read; no read permission for 'qaggFUM'". In fact, qaggFUM is
perfectly readable by that user.
This problem is more clearly shown at Tools->Security->User and Group
Permissions... With the old database, all users may view all
permissions up to but not including database permission (not desirable
itself, but that's another story...). With the new database, you get
the error "You can't view this object's permissions" and then it tells
you that you have to have Administer (ie top level) permission before
you can read the permission!!
Another thread (link below) tentatively concluded that this behaviour
might have something to do with upgrading an A97 workgroup to A2K (it
works) as against creating the workgroup under A2K (doesn't work). My
experience backs up this theory.
Has this been proved to be the case? Is there no other way to discover
whether a query is readable except by trying to read it? Can anyone
suggest a work-around?
http://groups.google.com.au/group/m...ccess.security"&rnum=1&hl=en#1f503325ac3ebba0
behaviour can be generalised to tables, forms & reports as well.
I have a secured Access 2000 database and wish to populate a combo box
with queries for which the current user has read permission or better.
I have done this before with success with an old database (Access 2K)
but my new database returns (for instance) error 3112 "record(s) cannot
be read; no read permission for 'qaggFUM'". In fact, qaggFUM is
perfectly readable by that user.
This problem is more clearly shown at Tools->Security->User and Group
Permissions... With the old database, all users may view all
permissions up to but not including database permission (not desirable
itself, but that's another story...). With the new database, you get
the error "You can't view this object's permissions" and then it tells
you that you have to have Administer (ie top level) permission before
you can read the permission!!
Another thread (link below) tentatively concluded that this behaviour
might have something to do with upgrading an A97 workgroup to A2K (it
works) as against creating the workgroup under A2K (doesn't work). My
experience backs up this theory.
Has this been proved to be the case? Is there no other way to discover
whether a query is readable except by trying to read it? Can anyone
suggest a work-around?
http://groups.google.com.au/group/m...ccess.security"&rnum=1&hl=en#1f503325ac3ebba0