Results 1 to 5 of 5
  1. #1
    New Lounger
    Join Date
    Jan 2003
    Location
    Pembroke Pines, Florida, USA
    Posts
    17
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Rolling out secured .MDB (Access 2002 SP1)

    Hi all,

    This seems rather simple, but I haven't found anything specifically addressing it.

    I've secured an .MDB on a shared networked drive. I've created an .MDW with users/groups, and assigned permissions as appropriate. Now, how to I roll out this and implement it?

    I realize I need to distribute the .MDW file I created to each of the users that will access the database. Is this as simple as Emailing the file to each user and having them save it on their local drive? If so, does it need to be saved in any particular folder? How does the .MDW know to open the .MDB file back at the networked shared drive?

    I would have assumed that all of this user info is saved within the .MDB but it seems that such is not the case, and it's getting me a bit confused. <img src=/S/brickwall.gif border=0 alt=brickwall width=25 height=15> <img src=/S/confused.gif border=0 alt=confused width=15 height=20>

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

    Re: Rolling out secured .MDB (Access 2002 SP1)

    You can give each user a private copy of the secured .mdw, or put it in a shared network folder.
    In both cases, create a shortcut that opens your database with the secured workgroup information file. The target of the shortcut should look like this:

    "C:Program FilesMicrosoft OfficeOffice10MSAccess.exe" "PatabasePathDatabaseName.mdb" /wrkgrp "Q:WorkgroupPathWorkgroupName.mdw"

    where you must substitute the appropriate paths and file names. You can use UNC paths instead of drive letters if you like.

    The users should open the database with this shortcut. If you have done the security right, you have taken away all rights from Admin in the database, so the users won't be able to do anything in the database if they open it directly (with a standard .mdw).

  3. #3
    New Lounger
    Join Date
    Jan 2003
    Location
    Pembroke Pines, Florida, USA
    Posts
    17
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Rolling out secured .MDB (Access 2002 SP1)

    Okay, that makes sense to me (surprise!). I was wondering how the workgroup file was "linked" to the database, and your shortcut target description answered that. I'll go test it out.

    Thanks Hans.

    PS - Yes, the Admin user has had all its rights revoked, but thanks for checking. <img src=/S/bow.gif border=0 alt=bow width=15 height=15>

  4. #4
    3 Star Lounger
    Join Date
    Sep 2002
    Posts
    294
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Rolling out secured .MDB (Access 2002 SP1)

    Just another thing for that shortcut, is that you can include in the filename the username and password

    (perhaps if you have a certain 'general usage' group), this auto logs you in and saves all that nasty password business.

    just add <font color=blue>/user USERNAME /pwd MYPASSWORD </font color=blue> to the end of Hans line.

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

    Re: Rolling out secured .MDB (Access 2002 SP1)

    However, that exposes the user name and password to anyone who checks the properties of the shortcut.
    Charlotte

Posting Permissions

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