Re: open exclusive for back end design

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: jk (jk_at_discussions.microsoft.com)
Date: 11/02/04 

Date: Tue, 2 Nov 2004 08:28:02 -0800

Thanks joan,

My objective for the be is to protect the tables from someone who could be
cruising the network and want to take a peek or delete an entry in the table.
The users need to do data entry on the fe and i am not too concerned on that
side but i do need for them to perform the data entry and i do not want
problems if i place user level security on the be in the network and all of a
sudden , they cant get in. I appreciate any direction from you to do it
right. thanks

"Joan Wild" wrote:

> jk wrote:
>
> > i have a db which is split fe/be on a network folder.This db had a
> > general password created through open exclusive but at the time of
> > the split, the linking did not work untill i removed the password on
> > the backend.It is sufficient to leave the fe with the general
> > password but i would like to secure the be with user level security.I
> > need to be careful since i already have quite a few users on this db
> > so i have yet to try it out...please advise on the above since it
> > seemed strange that a password would affect the linking manager.
>
> If you want to go with the database password (very easy to crack, by the
> way), you can open the backend and set the password. Then open the
> frontend, and delete the links. Then use File, Get External Data, Link to
> create the links again - this time you will be prompted for the backend
> password, which will be saved with the links.
>
> If you want to implement user level security on the backend, you can still
> do so. Follow the steps outlined in the security FAQ. If you are going to
> leave the frontend unsecured, then you likely will not want to create your
> own groups for the backend. Just assign the limited rights you need to the
> Users Group. You could even deny permission entirely on the backend tables,
> and use RWOP (run with owner permissions) queries in the frontend. This
> would mean securing the frontend as well.
>
> Security FAQ
> http://support.microsoft.com/?id=207793
>
> Security Whitepaper
> http://support.microsoft.com/?id=148555
>
> I've also outlined the detailed steps at
> www.jmwild.com/AccessSecurity.htm
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
>

Relevant Pages

  • Re: open exclusive for back end design
    ... you can open the backend and set the password. ... frontend, and delete the links. ... If you want to implement user level security on the backend, ... Follow the steps outlined in the security FAQ. ...
    (microsoft.public.access.security)
  • Re: READ ONLY ON NETWORK
    ... database into two components: frontend and backend. ... what you want to apply for security is called User Level ...
    (microsoft.public.access.queries)
  • Re: How do I apply security to two dbs using the same secure mdw?
    ... > gone through and set security on the frontend so that the ... > database can't be accessed with the standard system.mdw ... > is can I give the backend database the same security ... Open your frontend and refresh the links to the backend, ...
    (microsoft.public.access.security)
  • Re: User security for ~120 organizations
    ... This is an appropriate use for User Level Security, ... populate the field in the tables with the value of CurrentUser() ... Should I try this with the user-level security wizard? ...
    (microsoft.public.access.security)
  • Re: A2007 Security
    ... enable the ShiftKey ByPass on my database? ... Create the bypass key property using the DDL argument so that only an ... administrator can change the setting (assumes you have set up user level ... security in A2000 prevented them from opening the tables or queries ...
    (comp.databases.ms-access)