Re: Users can import

From: Joan Wild (jwild_at_nospamtyenet.com)
Date: 09/02/04 

Date: Thu, 2 Sep 2004 10:02:36 -0400

Mark wrote:
> I have a FE/BE database which is built on Access security. On top of
> this, I have also added my own security so that each usert (about 50)
> has their own userid. I have disabled the shift key on startup and
> was confident that it was secure. However, I have found that somone
> has been tampering with data which they should not have access to.
> After weeks of trying to figure out how it was done I have found that
> they did it by creating a new database whilst joined to my workgroup
> and then importing all the tables. Because that startup options are
> not set the same as mine, they can open up all of the tables they
> have read access on.
>
> Is there anyway that I can prevent users
> A) creating a new database whilst joined to my workgroup
> or
> B) Importing tables from my database?

I don't believe you can prevent them from creating a new database, but you
can deny them permission to your tables and use queries set to Run with
owner permissions for all data interaction via forms/reports.

Without permission to the tables, they won't be able to import/link.

Read section 18 and 24 of the security FAQ
 http://support.microsoft.com/?id=207793 

-- 
Joan Wild
Microsoft Access MVP

Relevant Pages

  • Re: How do I make Access a read only database?
    ... The most involved is to set up Access security, and assign permission to ... Disadvantage: Not really secure if you have savvy nosy users. ... >I have a Access 2002 database which various people can enter and add data, ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Bulletproofing database with .mde file
    ... malicious intent who is also a legitimate user of your database (ie. has the required folder ... "Normal users (in any workgroup file) will not be able to change the setting." ... that Access security simply raises the bar. ... John made no indication that his database was secure, ...
    (microsoft.public.access.security)
  • Re: Bulletproofing database with .mde file
    ... malicious intent who is also a legitimate user of your database (ie. has the required folder ... "Normal users (in any workgroup file) will not be able to change the setting." ... that Access security simply raises the bar. ... John made no indication that his database was secure, ...
    (microsoft.public.access.gettingstarted)
  • Re: Password HELP!!!!!!!
    ... > administrative account, and then am able to open databases ... > prompt for all ... >>Access Security: www.ltcomputerdesigns.com/Security.htm ... >>> of an extra database so I couldn't screw anything up, ...
    (microsoft.public.access.gettingstarted)
  • Re: Adding a database to existing workgroup file
    ... I was reading about splitting a database on your site just before I opened ... I think I'm going to have to study Access security in more depth using the ... > links to the tables in the backend. ... > the frontend exclusively to make design changes.) ...
    (microsoft.public.access.security)