K
kiln
I'm running a dual mdw secured access 2000 sp3 setup. I'm in line with
the secfaq, using faq_SetPermissions().
Now I'm seeing a new abberation. All of the queries have been set to
rwop. The query owner is an admins group member. But, all queries in the
front end are read only if I am logged in as a less empowered group
member. I've never seen this before. If I set the allow one of these
queires to be changable by that lower perms group member, and I open
that query in design mode, setting the run perms to Users allows the
query to run fully editable. Like, this is backwards. The table in the
query has to be set to allow viewing to of course by this user etc.
Can anyone imagine what might be behind this?
the secfaq, using faq_SetPermissions().
Now I'm seeing a new abberation. All of the queries have been set to
rwop. The query owner is an admins group member. But, all queries in the
front end are read only if I am logged in as a less empowered group
member. I've never seen this before. If I set the allow one of these
queires to be changable by that lower perms group member, and I open
that query in design mode, setting the run perms to Users allows the
query to run fully editable. Like, this is backwards. The table in the
query has to be set to allow viewing to of course by this user etc.
Can anyone imagine what might be behind this?