Results 1 to 12 of 12
  1. #1
    5 Star Lounger
    Join Date
    Jan 2001
    Posts
    1,119
    Thanks
    0
    Thanked 0 Times in 0 Posts

    splitting and securing a database (2000)

    Are there step by step directions to split a database? Do you secure a database first or can you split a database and then secure it. When you split a database, can you put the front end on a share drive and then send everyone a link to it? How do I maintain the queries, forms and reports in a split database? Do I keep a copy of the front end to add queries and reports to and then refresh the link? How do you relink the tables. As you can see, I don't know a thing about security or splitting a database but I think I am going to have to do this soon. I got some step by step directions for "Access 97/2000 Security Step by Step" at www.jmwild.com/security97.htm.. What if I don't split the database and put it on a share drive and send everyone a link to it? Will it be slower than if everyone has a copy of the front end? Any answers you can provide will be appreciated. Thanks for your help.

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: splitting and securing a database (2000)

    Moderator <!profile=WendellB>WendellB<!/profile> has a tutorial on his website: Why Split a Database?. It answers several of your questions.

    In general, it is advisable to create a single backend database containing only tables, and to give each user his/her own copy of the frontend with queries, forms and reports, and links to the table in the backend.

  3. #3
    5 Star Lounger
    Join Date
    Jan 2001
    Posts
    1,119
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: splitting and securing a database (2000)

    How do I (who will create the queries, forms and reports) maintain this data. If I have to run queries that make tables and delete etc, how do I do this if they are in the front end. Everyone who will be using the front end won't be creating queries, forms or reports - I will be doing this. Am I way off in my thinking?

  4. #4
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Virginia, USA
    Posts
    1,560
    Thanks
    37
    Thanked 1 Time in 1 Post

    Re: splitting and securing a database (2000)

    I am by no means an Access expert, and I know little about securing a database. However, I've done some of the stuff you want to do, so I'll share my <img src=/S/2cents.gif border=0 alt=2cents width=15 height=15>. The following reflects the experience I had deploying and maintaining a small database with about six users. It was nothing fancy.

    I've never read anything advising one to put the whole database into a shared drive and inviting users to go there. You want to split it into FE/BE. The BE (backend) holds just the tables

  5. #5
    5 Star Lounger
    Join Date
    Nov 2004
    Location
    Wilmington, North Carolina, USA
    Posts
    1,196
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: splitting and securing a database (2000)

    Linda, if your changes won't affect the end users, I would say that you could distribute your front end (Secured), and keep an unsecured copy for yourself to run the queries, etc....

    I'm attaching a database that has an example of how to keep database objects in sync with a master copy residing on a network, I know I got the link to the site where I downloaded this database here at Woody's, but I can't remember the site.
    ____________________________
    Jeremy
    "If you spend more on coffee than on IT security, then you will be hacked. What&#39;s more, you deserve to be hacked." -Richard Clarke

  6. #6
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: splitting and securing a database (2000)

    An unsecured copy shouldn't be able to do anything if the rest of the application is properly secured, Jeremy. Part of securing a database app is taking all the permissions away from the Admin user and taking the Admin user out of the Admins group. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

  7. #7
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: splitting and securing a database (2000)

    In addition to the comments already posted, you might find our User Security Tutorial useful, and Jack MacDonald's User Security paper contains a much more detailed look at securing a database.
    Wendell

  8. #8
    5 Star Lounger
    Join Date
    Jan 2001
    Posts
    1,119
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: splitting and securing a database (2000)

    I guess I don't really want to have to maintain this database too much. My job is ad hoc reporting and just doing that keeps me hopping. Now I have 6 databases that I have to maintain. The other databases are just repositories for reports which works fine. Now I have this database that will be used for data entry and has a lot more maintenance. If I split the database and everyone will be data entering - will the reports reflect everyone's records as they are edited and added? Will the form show all records real time? I am sorry if I sound dumb but I don't want to make this harder than I have to. I just want to make sure if I split this database, I am giving them what they want to see real time. If they put the front end on their C drive, how would the link to the back end work?

  9. #9
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: splitting and securing a database (2000)

    Whether the database is split into frontend and backend or not makes no difference for what the users see. It also doesn't matter whether the frontend is stored on a network drive or on a local drive; the table links to the backend "know" the location of the kackend database. It's best to use a UNC path (of the form serversharefolder...) rather than a path with a drive letter (of the form P:folder...), so that you are not dependent on the drive mappings of individual users.

  10. #10
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: splitting and securing a database (2000)

    <hr>I know I got the link to the site where I downloaded this database here at Woody's, but I can't remember the site. <hr>
    Here's the link

  11. #11
    5 Star Lounger
    Join Date
    Apr 2003
    Location
    Hampshire, United Kingdom
    Posts
    602
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: splitting and securing a database (2000)

    <hr>the table links to the backend "know" the location of the kackend database<hr>
    <img src=/S/shocked.gif border=0 alt=shocked width=15 height=15> <img src=/S/whisper.gif border=0 alt=whisper width=29 height=17>Now that's a new name for it! <img src=/S/laugh.gif border=0 alt=laugh width=15 height=15>
    Waggers
    If at first you do succeed, you&#39;ve probably missed something.

  12. #12
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: splitting and securing a database (2000)

    <img src=/S/blush.gif border=0 alt=blush width=15 height=15>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •