N
neeraj
I have implemented user level security on my database using wizard. There is
one report in this database which requires a macro to be run first. The first
step in this macro is a make table query. This query makes a table, say
Table1. I have created a group, say Group1 which has a few users say user1,
user2. When I am logged in as user1 and I try to open the report or run this
macro on its own, it gives an error mesage saying 'could not create; no
modify permission for table or query 'Table1'. Till here, Group1 had only
read read data and read design permission on all tables in the database.
After I got this error message, I logged in as the administrator say Admin1,
then went on to provide all permissions to Group1 for Table1 including modify
design but excluding administer. I then logged back as User1 and ran the
macro again but it gives the same error message. Everytime a make table query
is run, it deletes that table first if it is already there, and User1 cant
create it. How can I resolve this? (I also observed that running the macro
while logged in as Admin1 created Table1 and changed the permissions of
Admin1 as a user for Table1 to all permissions including administer from none)
one report in this database which requires a macro to be run first. The first
step in this macro is a make table query. This query makes a table, say
Table1. I have created a group, say Group1 which has a few users say user1,
user2. When I am logged in as user1 and I try to open the report or run this
macro on its own, it gives an error mesage saying 'could not create; no
modify permission for table or query 'Table1'. Till here, Group1 had only
read read data and read design permission on all tables in the database.
After I got this error message, I logged in as the administrator say Admin1,
then went on to provide all permissions to Group1 for Table1 including modify
design but excluding administer. I then logged back as User1 and ran the
macro again but it gives the same error message. Everytime a make table query
is run, it deletes that table first if it is already there, and User1 cant
create it. How can I resolve this? (I also observed that running the macro
while logged in as Admin1 created Table1 and changed the permissions of
Admin1 as a user for Table1 to all permissions including administer from none)