Read only report

[Guest]

I am trying to do very simple security. Three groups: Admin, Editors (without
design capabilities), and those that can only add information. However, when
I go through the security wizard and User and Group Permission the Editors
and "adders" cannot view reports. I think this has to do with a query I made
for the reports that deletes old information. Is there any way to have all
groups view reports and still have reports delete information that is not the
newest?

 

[Joan Wild]

One wouldn't normally delete old information in a database. Your query
should include criteria that pulls only the recent data.

The users that view a report based on this query, need read data permission
on the query and Open permission on the report.

 

[Guest]

Thank you for the reply Joan.

The problem is that I am trying to do the security for the database but my
coworker created it. This is what she says:

“I guess I didn’t explain correctly what my queries do. The way the reports
get generated are through Macros, which run queries and the first query is
always “Make a Table†and then the rest are “Append Queryâ€. So every time a
macro runs, the “Make a table query†deletes the old table and creates a new
one. Should I not use “Make a Table Query�

So basically every part of the database security is working besides the
report. A window pops up that says:

Action Failed

Macro Name:
Macro2)Rejected Ideas

Condition:
True

Action Name:
OpenQuery

Arguments:
2)a Get Rejected Ideas q, Datasheet, Edit

….and there are 3 buttons to the right: Step, Halt, Continue. Step and
Continue are inactive and Halt is the only one you can click on. When I click
halt I get a window:

Microsoft Office Access
There was an error executing the command.

Thank you for the help, Anne.

 

[Joan Wild]

OK, I still find that very odd. You shouldn't need to create a table, and
append to it in order to print a report. A report should be able to use a
query (with the necessary criteria). Instead of using a make table, you
could use a delete query (to empty the table), followed by the append query
to populate the table.

You're running into the problem that users likely don't own the table, and
so can't delete it.

If you use RWOP queries (for the delete and append queries), users wouldn't
need any permission on the table, but you'd grant delete permission on the
delete query, and insert permission on the append query.

 

[Guest]

Thank you sooo much! It worked.

OK, I still find that very odd. You shouldn't need to create a table, and
append to it in order to print a report. A report should be able to use a
query (with the necessary criteria). Instead of using a make table, you
could use a delete query (to empty the table), followed by the append query
to populate the table.

You're running into the problem that users likely don't own the table, and
so can't delete it.

If you use RWOP queries (for the delete and append queries), users wouldn't
need any permission on the table, but you'd grant delete permission on the
delete query, and insert permission on the append query.