User Groups & Permissions

[dtjbocala]

I have a database that has several users. I did ok setting up admin rights
for a couple users, but the rest of the users I am having a problem. It is
the create table query that runs reports that is giving me a hard time. I do
not want my general users to be able to modify Forms, Queries, Reports &
Macros. But they need to be able to run these make table queries. Does this
make sense? I tried full permission, but the users can get in and edit
forms. Is this something simple that I cannot find? Thanks as always.

 

[Larry Daugherty]

In most cases you'd want your users to be running the MDE form of your
FrontEnd anyway. In an MDE, none of those things can be modified but
they can run any kind of query.

HTH
--
-Larry-
--

I have a database that has several users. I did ok setting up admin rights
for a couple users, but the rest of the users I am having a problem. It is
the create table query that runs reports that is giving me a hard time. I do
not want my general users to be able to modify Forms, Queries, Reports &
Macros. But they need to be able to run these make table queries. Does this
make sense? I tried full permission, but the users can get in and edit
forms. Is this something simple that I cannot find? Thanks as

always.

 

[Larry Linson]

Access Workgroup Security is addressed in detail, without any "chaff" or
"filler", in a Security FAQ paper, which can be downloaded from the
following link in the Microsoft Knowledge Base:

http://support.microsoft.com/kb/207793/en-us

Another KB article, with a similar reference, is:

http://support.microsoft.com/kb/165009/en-us

Read carefully, it is not "trivially simple" and "every word counts".

Larry Linson
Microsoft Access MVP

 

[John W. Vinson]

I have a database that has several users. I did ok setting up admin rights
for a couple users, but the rest of the users I am having a problem. It is
the create table query that runs reports that is giving me a hard time. I do
not want my general users to be able to modify Forms, Queries, Reports &
Macros. But they need to be able to run these make table queries. Does this
make sense? I tried full permission, but the users can get in and edit
forms. Is this something simple that I cannot find? Thanks as always.

One suggestion: lose your MakeTable queries.

If you're assuming that you must run a MakeTable query, and then base a report
on that new table, your assumption may need revision! It's not only possible,
it's very routine to base a Report on a Select Query.

Try changing your MakeTable query back into a simple Select query and use that
Query as the recordsource for your Report.

If you feel that it is in fact necessary to run the MakeTable (with its bloat,
performance loss, and overhead) please explain why; I'm sure there are ways
around it (perhaps making the table in a separate linked temporary backend
database).

John W. Vinson [MVP]

 

[Aaron Kempf]

I wouldn't use Access Security

it doesn't work half of the days of the week

go and buy a book on SQL Server and do it right-- move to ADP

 

[John W. Vinson]

Read carefully, it is not "trivially simple" and "every word counts".

I often suggest:

Read the whitepaper, carefully.

Get a good night's sleep.

Read the whitepaper - AGAIN. Even more carefully!

Print out a copy and use a highlighter to mark off each step as you secure
your database.

It's pretty good... but easy is NOT one of its features!

<g>

John W. Vinson [MVP]

 

[Joan Wild]

It is likely that you don't need the make table query(ies). Can't you just base your report on a select query?

More specifics on the permissions and permission errors would help.