Results 1 to 8 of 8
  1. #1
    2 Star Lounger
    Join Date
    Mar 2003
    Location
    Canton, Ohio, USA
    Posts
    103
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Split Database (2000)

    I have a split database. Today I spent all day making code, security and layout changes to the front end. After saving everything, I copied the front-end to another workstation. None of the work that I did today comes up when I open the application on the second workstation. What I get is the way it was before I started working on it this morning. What am I missing? What am I doing wrong?

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

    Re: Split Database (2000)

    Security information on database objects (who may do what) is kept in the database, but information on users is kept in the workgroup information file. This is a file with extension .mdw. Its default name is System.mdw and its default location depends on your Windows version, but it is on your hard disk. The secured users you created exist in your System.mdw, but the other workstation has its own System.mdw.

    I strongly recommend that you download and study ACC: Microsoft Access Security FAQ Available in Download Center. It is an excellent overview of Access security.

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

    Re: Split Database (2000)

    In addition to Hans' comments, you might want to look at the security tutorial on our website.
    Wendell

  4. #4
    2 Star Lounger
    Join Date
    Mar 2003
    Location
    Canton, Ohio, USA
    Posts
    103
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Split Database (2000)

    Thanks guys, I'll do that. Would not moving the security mdw file also effect the design changes I did today not showing up on the second workstation? Also, does this mdw file have to go in some special place on each workstation I copy the application to? Maybe all this will be in the information you had me download.

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

    Re: Split Database (2000)

    Both the Microsoft documentation and Wendell's eminent tutorial will tell you about this. You can also do a search for "mdw" (without the quotes) in this Forum, you'll find several threads dealing with this.

    The basic idea is that you should create a shortcut that opens the database together with the secured .mdw file.

  6. #6
    3 Star Lounger
    Join Date
    Jun 2001
    Location
    Maidstone, Kent, England
    Posts
    398
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Split Database (2000)

    This may be a silly question <img src=/S/smile.gif border=0 alt=smile width=15 height=15> but did you copy the right database? If you used the security wizard I believe it would have created a new secure db, which is probably where your changes are, and you copied the original unsecured db to the new machine.

  7. #7
    4 Star Lounger
    Join Date
    Aug 2002
    Location
    Dallas, Texas, USA
    Posts
    594
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Split Database (2000)

    Yes, what you are asking for should be in the information posted to you. However, just a quick 'comparison'. Access User level security is a lot like NT domain security. Names and Passwords are stored in the .mdw, just like NT's SAM database. Permissions are stored in the database, just like they are stored within the actual file/folder system in NT. Interaction between the two is done with a 'hash'. A hash is a 'string' that is made from the .mdw file. So you can change the password in the .mdw, and the user can still access the data in the database, since the hash is the same, just getting the 'hash' requires a new password.

    The 'hash' is made from the UserName and the 'ID' that you enter when you create a new User or Group. If you make an identical group (name and ID), in another .mdw, that user/group will work in the same database, from either .mdw. (Because the 'hash' will be the same). The default .mdw (System.mdw...usually in your System32 folder) has an Admin account. You cannot change the ID, because the Admin account is prebuilt, thus you never get the option to put in an ID. Thus, if you change the password in one .mdw for the Admin account, then set all of your security in your database for that Admin user......if someone comes along and uses another .mdw, their Admin account gets the same permissions (regardless of the password). The really big catch is that when you make an .mdw, it automatically creates an Admin account, with no password. So if you are on a machine, that has it's system.mdw's Admin account with a password set. All you have to do, is run wrkgadm, make a new .mdw, (which automatically joins you to the new .mdw), and now open that 'secured' database, and you're in.

    Hopefully that is sorta easy to understand. The documentation is a little wordy/round about. I'm tired though, so I may have confused you more. <img src=/S/evilgrin.gif border=0 alt=evilgrin width=15 height=15>

  8. #8
    2 Star Lounger
    Join Date
    Mar 2003
    Location
    Canton, Ohio, USA
    Posts
    103
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Split Database (2000)

    Thanks guys for all your help. I have learned a lot and it has been very useful.

Posting Permissions

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