Re: RWOP /table permissions question

With Admins permissions, yes they can. Put them in a different group.


--
Joan Wild
Microsoft Access MVP
"Beth" <Invalid@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3wTMh.10238$Um6.4302@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Joan and Keith,
Thank you for the comments. I have the database window hidden on the
front end and shift bypass handeld from Albert's utility.
However, can't the users with admin rights still create a new database and
import the queries and tables to see the structure?

Thanks,
Beth


"Joan Wild" <jwild@xxxxxxxxxxxxxxxx> wrote in message
news:%23YQ3RjKbHHA.1220@xxxxxxxxxxxxxxxxxxxxxxx
In addition to Keith's comments regarding locking down the interface,
remove all permissions from the tables. Create a RWOP query for each
table. Now base all your SQL statements on these queries rather than the
tables. Your users will need appropriate permissions on the RWOP
queries, but not on the tables.

--
Joan Wild
Microsoft Access MVP
"Beth" <Invalid@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:XtxMh.2297$Kd3.541@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have a database in Access 2000, split into FE/BE and have security set
on both sides. The file is converted to an mde before shipping.
I am trying to protect the integrity of the program as much as possible
as I have some admin users trying to some bad things to the program. In
doing that I am running into what appear to be a conflict and I am
hoping someone can tell me a way around this conflict.
I have removed all queries from the database and instead put SQL
statements into the rowsource for every combobox, form, and report. To
do that it appears I have to leave data access on the backend table,
which includes read design by default. That is allowing my admin users
to import the tables into their own front end, thereby bypassing all the
data validation I have setup in my forms. It also lets them learn how
my tables are setup.
On the other hand, I can remove all permissions from the tables in the
backend, but I can't use the SQL statements and have to use queries set
to RWOP. That then leaves the queries available for import to other
databases.
While I don't want to give up the information about the tables, I think
more development work and intelligence goes into my queries, so I don't
want to have users see the design on those.

Am I missing something in the security setup or is there a way around
this conflict? The only answer I am seeing is to lock the tables and
convert to VB with connection strings.

Any suggestions are welcome.
Beth







.

Relevant Pages

  • Re: User has group permissions to object, but still denied access.
    ... permissions to those query objects. ... The owners for the other 68 queries can be changed. ... may have been some of the original queries created in the database. ... Regarding the security, the database was converted from an Access 97 ...
    (microsoft.public.access.security)
  • Re: RWOP /table permissions question
    ... Look in the security FAQ. ... without them needing permissions on the tables. ... Microsoft Access MVP ... Now base all your SQL statements on these queries rather than ...
    (microsoft.public.access.security)
  • Re: User has group permissions to object, but still denied access.
    ... specific queries is identical to queries that she does have the ability to ... permissions depending on where the file is, it means she's either opening the ... about 80 queries in the database, and I haven't been able to find a pattern ... The Admins group was given full permissions. ...
    (microsoft.public.access.security)
  • Re: Setting up user group that can create and save select queries
    ... You are having this problem because of a bug with the security wizard. ... Put your users in one of the wizard-created groups, as well as the group you created for them, and they'll be able to save their queries. ... Give the users modify permissions on the query to change the SQL property in code. ... The application database used to enter and update the data; ...
    (microsoft.public.access.security)
  • Re: no read definitions on query
    ... If queries, then the users need at least read data permissions in order to ... If you had no permissions on the queries/tables, ... level security on a database. ... not the user tried to access the query. ...
    (microsoft.public.access.security)
Loading