A problem with RWOP Security?

[christopher_mouse]

I have a split Access 97 database that I've been asked to secure. The
data is sensitive and users include programmers who are routinely
accessing the data directly, so I plan to remove all permissions from
the tables in the backend and then create RWOP queries to retrieve all
the fields in the tables so users are limited to the column/row access
that I design in these queries.

I also plan to remove permissions for users to create new queries to
stop them from creating their own new queries (as I know some of them
will) based on my RWOP queries which would effectively allow them to do
anything the like (is this correct?).

BUT!!! a lot of the code in this database creates named querydefs in
the code, if I turn off user permissions to create new queries won't
all this code stop working? If so does that mean the only way round
this problem is to remove all these queries from code?

Thanks in advance

Chris

[Tom van Stiphout]

On 18 Apr 2005 05:41:45 -0700, "ch***************@yahoo.co.uk"
<ch***************@yahoo.co.uk> wrote:

Yes, those created querydefs will stop working.

Additionally there are password cracker programs available that can
defeat Access security. If you really want it to be secure, a SQL
Server (or MSDE) backend is much better.

-Tom.

I have a split Access 97 database that I've been asked to secure. The
data is sensitive and users include programmers who are routinely
accessing the data directly, so I plan to remove all permissions from
the tables in the backend and then create RWOP queries to retrieve all
the fields in the tables so users are limited to the column/row access
that I design in these queries.

I also plan to remove permissions for users to create new queries to
stop them from creating their own new queries (as I know some of them
will) based on my RWOP queries which would effectively allow them to do
anything the like (is this correct?).

BUT!!! a lot of the code in this database creates named querydefs in
the code, if I turn off user permissions to create new queries won't
all this code stop working? If so does that mean the only way round
this problem is to remove all these queries from code?

Thanks in advance

Chris