Re: RWOP /table permissions question
- From: "Joan Wild" <jwild@xxxxxxxxxxxxxxxx>
- Date: Fri, 23 Mar 2007 15:01:44 -0400
Look in the security FAQ. There is code you can use to relink tables
without them needing permissions on the tables.
http://support.microsoft.com/?id=207793
--
Joan Wild
Microsoft Access MVP
"Beth" <Invalid@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3eVMh.729$rO7.480@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Joan,
Thank you for your responses.
I don't think I am stating everything I need to. Sorry.
They aren't in the default admin group. I moved them into my custom
"MyAdmins" group. That group has to be able to relink tables from the
different backends to the main front end, so had to give them more
privileges on the program. Those users have those permissions and are
familiar with the security file.
I think that would let them create their new file and import the objects.
Is there a way around that?
Lori
"Joan Wild" <jwild@xxxxxxxxxxxxxxxx> wrote in message
news:Oj2OYPXbHHA.2300@xxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- RWOP /table permissions question
- From: Beth
- Re: RWOP /table permissions question
- From: Joan Wild
- Re: RWOP /table permissions question
- From: Beth
- Re: RWOP /table permissions question
- From: Joan Wild
- Re: RWOP /table permissions question
- From: Beth
- RWOP /table permissions question
- Prev by Date: Re: RWOP /table permissions question
- Next by Date: Re: Shared v. Exclusive Access
- Previous by thread: Re: RWOP /table permissions question
- Next by thread: Access 2003 and Access 2000
- Index(es):
Relevant Pages
|
Loading