A problem with RWOP Security?

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • christopher_mouse@yahoo.co.uk
    #1

    A problem with RWOP Security?

    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

    Tags: None
    • Tom van Stiphout
      #2
      Re: A problem with RWOP Security?

      On 18 Apr 2005 05:41:45 -0700, "christopher_mo use@yahoo.co.uk "
      <christopher_mo use@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.

      [color=blue]
      >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[/color]

        Comment

        Previous template Next
        Working...