Results 1 to 9 of 9
  1. #1
    Star Lounger
    Join Date
    Jan 2003
    Location
    Canberra, Australian Capital Territory, Australia
    Posts
    78
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    I have just converted an Access2 database to Access2000. I was wondering how to upgrade the SYSTEM.MDA to the SYSTEM.MDW? The error that I get is if I choose Tools/Security/User and Group Permissions/ it says "Record(s) cannot be read; no read permissons on 'MSysAccounts'"

    Thanks.

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

    Re: Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    Try converting it to a 97 format first. But why are you trying to convert a System.mda? You don't normally build security using the System mda/mdw, you use a copy. If there is no security on the Access 2 database, you don't need to conver the System.mda at all.
    Charlotte

  3. #3
    Star Lounger
    Join Date
    Jan 2003
    Location
    Canberra, Australian Capital Territory, Australia
    Posts
    78
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    There was some security on the Access2 database, and the system.mda file contains the user accounts and passwords. Now that the database is in Access2000, the error occurs saying there is no permission to the "mSysAccounts" table.
    Thanks

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

    Re: Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    Are you attaching to the System.mda file from the WorkGroup Manager (or via the shortcut that starts the database)? In my experience that should work and allow the users to still log in and do things. Access should not have allowed you to convert the database if it was truly secured without attaching to the security file. I also believe there is a process documented in the Access 97 Help files for converting a System.mda file to a System.mdw file. If you don't have a copy of 97 to look at, I'll see if I can dig it out for you - the principal advantage of the MDW format is it makes the database a bit more secure.
    Wendell

  5. #5
    Star Lounger
    Join Date
    Jan 2003
    Location
    Canberra, Australian Capital Territory, Australia
    Posts
    78
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    I attached the system.mda using the Workgroup manager. Everything was working okay, however, when I installed the application on a network computer I wasn't able to link the tables. The error said that the database was opened exclusively by another user. (The network computer does have CREATE permissions on the folder, so it doesn't seem to be a locking issue.)

    The reason I started looking at the security is that when selecting Tools/Security/User and Group Permissions/ there are no users listed, and the error about no read permission on 'MSysAccounts' keeps popping up. I was thinking that this might be interfering with linking the tables, since admin isn't the owner of the tables.

    If you can find a copy of the Access97 instructions for converting the system.mda to a system.mdw, that would be fantastic. I really appreciate your help.

  6. #6
    Bronze Lounger
    Join Date
    Nov 2001
    Location
    Arlington, Virginia, USA
    Posts
    1,394
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    There's really no good way to "convert" a workgroup information file; for example, see MSKB 282357:

    ACC2002: Error Messages When You Convert Workgroup Information (.mdw) File to Access 2002

    Though this applies to later version of Access, most of info still applicable. Excerpt:

    "You should not convert workgroup information files by using the Convert Database utilities in Access. There are two reasons for this: First, there have been security improvements in Microsoft Jet 4.0 workgroup information files, and to take advantage of these improvements, you must re-create the workgroup information file.

    "Second, even though workgroup information files are standard Jet database files, they do not contain an Access project storage for forms, reports, macros, and modules. When Access attempts to convert the file, it generates error messages because it cannot locate the Access project storage for these objects. The MSysAccessObjects table is the table that contains the Access project storage, and this table exists only in databases that have been opened in Access."

    The Access 97 Developer's Handbook, Chap 14, "Migrating Secured Databases to Access 97" lists 3 strategies, summarized below:

    (1) Convert secured db while joined to existing ACC 2.0 workgroup file (.MDA); continue to use 2.0 workgroup file. You won't be able to take advantage of newer security features.

    (2) Convert secured db; then create new ACC 97 .MDW file using identical Workgroup ID & create same accounts using identical PID's used for 2.0 workgroup file. Requires you have written record of WID/PID's used to create the original .MDA file.

    (3) Document exisiting security accounts & permissions; unsecure db, then convert to 97; create new .MDW file with new PID's & secure converted db with new .MDW file. This requires the most work, but would be necessary if you do not have PID's, etc used to create original .MDA file.

    I no longer use ACC 97, & never had to convert secured 2.0 db to 97; but did convert numerous secured 97 db's to A2K. I did it the hard way: unsecured db in 97, converted to 2K, recreated workgroup file in 2K, resecured 2K db with new .MDW file. This was more work than simply "converting" 97 .MDW file, which did NOT work for reasons outlined in MSKB article. FWIW, the attached Word doc is copy of the instructions from ACC 97 Help file for converting workgroup information file from a previous version of Microsoft Access. It basically states that you should create a new workgroup file - you can't simply "convert" it to newer format.

    HTH
    Attached Files Attached Files

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

    Re: Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    Mark is correct - the current view is that converting a workgroup file is problematic. Actually in digging, I believe it was Access 95 that introduced the .MDW version of the file, and the info on converting was in that, but I no longer have that version available. One other document (also referenced in our tutorial) is available for download in <!mskb=165000>Microsoft Knowledge Base Article 165000<!/mskb>, and it mentions tinkering with an Access 2.0 system.mda in Access, but I would agree that the best approach is to recreate the file in 2000 format. If you are able to import objects from the old database into a new 2000 database that you create, you should then end up with ownership of the objects.
    Wendell

  8. #8
    Star Lounger
    Join Date
    Jan 2003
    Location
    Canberra, Australian Capital Territory, Australia
    Posts
    78
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    Thank you very much. I created a new database and imported everything into it and now admin is the owner of all the objects. So I can get rid of the old system.mda file.

    I couldn't have done it without your help! <img src=/S/basket.gif border=0 alt=basket width=58 height=52>

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

    Re: Convert SYSTEM.MDA to SYSTEM.MDW (Access2000)

    Just a small follow on now that you've successfully upgraded the database. If you truly secure the new database, make sure and either keep a backup copy of your System.MDW file (or whatever you choose to name it), or alternatively that you write down both the UserName and Personal ID for all Users and Groups that you create. If you have that you can recreate the security file. Without one or the other, if the security file is lost or destroyed, and the database has been completely secured, you won't be able to use the process you just went through.
    Wendell

Posting Permissions

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