Jet User-Level Security

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • plaguna
    New Member
    • May 2008
    • 58

    #1

    Jet User-Level Security

    Basically I have Three questions about Jet U-L Security:

    1.Every time I create new Groups, new Users and Permissions using the User and Group Accounts dialog box, It creates User security for every single DB Access file I have in my system. How can I get a Jet User-Level Security only for the current opened file without using the User-Level Security Wizard?.

    2. Also, Is there a way to view and make changes to Groups and Users opening the User and Group Accounts and Permissions dialog boxes after the Group and its Users are created with the U-L Security Wizard?

    I feel too limited using the Wizard and I rather use the User and Group Accounts and Permissions dialog boxes to manipulate Groups and Users.

    3. If I create User-Level Security with MS ACCESS 2007 at a Network level. Am I going to have compatibilities problems with 2000 version workstations?

    If anybody can give me a hint about these concerns, it would be great.
    Thank you in advance,
    Plaguna
  • ADezii
    Recognized Expert Expert
    • Apr 2006
    • 8834

    #2
    1. You can use the /wrkgrp Command Line Switch to open a Database with a specific Workgroup Information File as in:
      Code:
      "C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\Program Files\Microsoft Office\Office\Samples\Northwind.mdb" /wrkgrp "C:\Test\Top_Secret.mdw"
    2. No matter what the mechanism by which you create your User and Group Accounts, they should all be able to be managed via the GUI (Tools ==> Security ==> Blah, Blah Blah...)

    Comment

    • plaguna
      New Member
      • May 2008
      • 58

      #3
      I think question #1 was not well explained. Let’s start all over again.
      I have MS Access 2007 (My Database files are saved as .mdb extension). I have no problem to create Users and Groups, and grant them specific Permissions. What I don’t understand is why when I create Password, and Permissions to allow or restrict the access of users and Groups to the objects in a specific Database file, (Ex: for only Sales.mdb) it creates security password for all (*.mdb) files. Some DB files don’t need any type of security password. The idea is to create User-Level Security and security passwords for individual Database files. I tried everything, and nothing works. Can anybody has an idea how to do this?
      Thank you in advance

      Plaguna

      Comment

      • Stewart Ross
        Recognized Expert Moderator Specialist
        • Feb 2008
        • 2545

        #4
        Hi Plaguna. Please do not double-post your questions. You have started a new thread linked here instead of being patient and waiting for a response to post #3.

        MODERATOR

        Comment

        • plaguna
          New Member
          • May 2008
          • 58

          #5
          I'm sorry about that

          Comment

          • ADezii
            Recognized Expert Expert
            • Apr 2006
            • 8834

            #6
            Originally posted by plaguna
            I think question #1 was not well explained. Let’s start all over again.
            I have MS Access 2007 (My Database files are saved as .mdb extension). I have no problem to create Users and Groups, and grant them specific Permissions. What I don’t understand is why when I create Password, and Permissions to allow or restrict the access of users and Groups to the objects in a specific Database file, (Ex: for only Sales.mdb) it creates security password for all (*.mdb) files. Some DB files don’t need any type of security password. The idea is to create User-Level Security and security passwords for individual Database files. I tried everything, and nothing works. Can anybody has an idea how to do this?
            Thank you in advance

            Plaguna
            Question #1 was well explained and the answer is still the same. When you establish a Security Mechanism via Users and Groups within an Access Database, it is 'Global' to Access and affects all Databases unless you specifically Join another Workgroup (say the generic System.mdw which is not secured). You cannot have a Secured and Unsecured Database working off the same Workgroup Information File.

            Comment

            • plaguna
              New Member
              • May 2008
              • 58

              #7
              Now I see what you mean. I'll try to solved it based on that concept.

              Thank you

              Comment

              Working...