Results 1 to 4 of 4

Thread: FE-BE security

  1. #1
    Join Date
    Jun 2006

    Unanswered: FE-BE security

    I have a database that has been split. I need to secure it such that people can access the front end, but not the back end. What has been happening is that even though everyone has their own copy of the front end on their own machine, they have been opening the back end and it prevents anyone else from opening their front end. What I have been trying to do is lock everyone out of the back end.

    I tried putting a password on the back end, then relinking the front end tables and inputting the password, and that works, except for some reason when I open the front end from my own hard drive, it creates a locked back end file on the server, which means no one else can open their front ends.


  2. #2
    Join Date
    Apr 2004
    outside the rim
    You can create a startup form on the back end that simply quits the application. If you are feeling generous, you can have the form display a message telling the user the error they've made and put the quit on the timer (give them say 5 or 10 seconds).

    You can disable special keys (such as the Control Break) and the Bypass Key.

    Note: this makes it very difficult to get into the back end. You will want to craft yourself a "back door". I generally have a "hot spot" on the form, such as an image, with an "On Click" event. When clicked, it checks the username and if the user is an IT person, will derail the quit command. If the user is not, then nothing visible to the user happens and it promptly quits after 5 seconds.

    As always, there are other methods; if you wait long enough, somebody will post their technique.

    have fun,

  3. #3
    Join Date
    Jun 2006
    I may have forgotten to mention that I am a novice at this, and although I know what you are talking about, I don't have a clue how to do it, and coding is far from one of my specialties.

  4. #4
    Join Date
    Feb 2004
    New Zealand
    Provided Answers: 5
    A little trick I do in the back end is write a macro autoexec to close the data base when it is open up.
    hope this help

    See clear as mud

    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB based on my own environment: vb6 sp5
    ASP based on my own environment: 5.6
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008

Posting Permissions

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