Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/170696

From BetaArchive Wiki

Article ID: 170696

Article Last Modified on 1/20/2007



APPLIES TO

  • Microsoft Access 97 Standard Edition



This article was previously published under Q170696

Moderate: Requires basic macro, coding, and interoperability skills.


SYMPTOMS

When you open an MDE file that was created from a secured database that contains modules, you may receive the following error message:

   Record(s) can't be read; no read permissions on 'MsysModules2'
                

CAUSE

This problem occurs because only the owner of the MDE file or a member of the Admins group when the MDE file was created can successfully open an MDE file created from a secured database that contains modules.

RESOLUTION

The following workaround allows your users to open the database. This workaround assumes that the database is secured, the MDE file has already been created, and you are currently using the workgroup file that was used when the MDE file was created.

  1. Start Microsoft Access and log on as an administrator.
  2. Open the MDE file, holding down the SHIFT key to prevent any AutoExec macros from running.
  3. On the Tools menu, click Options, and then click the View tab. Make sure the System Objects check box is selected.
  4. On the Tools menu, click Security, and then click User And Group Permissions.
  5. In the User And Group Permissions dialog box, click Groups, and then select Table in the Object Type combo box.
  6. In the User/Group name list box, select Users.
  7. In the Object Name list box, select MsysModules2.
  8. Select the following permissions for the table:

        - Read Data
        - Read Design
        - Update Data
        - Insert Data
        - Delete Data
                            
  9. Click OK to close the User And Group Permissions box. Your users should now be able to open the MDE file.


STATUS

Microsoft has confirmed this to be a problem in Microsoft Access 97.

MORE INFORMATION

Steps to Reproduce Problem


  1. Quit Microsoft Access if it is running, and then make a backup copy of your System.mdw file.
  2. Using the Workgroup Administrator program, create and join a new workgroup. Make note of the Name, Organization, and Workgroup ID values used to create the new workgroup. These values are combined to create the group Security ID (SID) for the Admins group.


NOTE: For information about creating a workgroup information file, search the Help Index for "workgroup information files, creating."

  1. Start Microsoft Access and activate the logon process by assigning a password for the Admin user.
  2. Create a new user and add the user to the Admins group.
  3. Create another user, but do not add this user to the Admins group.
  4. Quit and restart Microsoft Access, logging on as the user you created in Step 4.
  5. Create a blank new database.
  6. Create a new module with any sample code.
  7. On the Tools menu, click Security, and then click User-Level Security Wizard.
  8. In the User-Level Security Wizard, click OK to accept the default settings. Click Yes to continue if you receive a warning about removing Admin from the Admins group.
  9. In the Destination Database dialog box, click Save to accept the default file name for the secured database.
  10. Click OK to the User-Level Security Wizard message that lets you know the database has been secured.
  11. Open the secured version of the database.
  12. On the Tools menu, point to Database Utilities, and then click Make MDE file. In the Save MDE As dialog box, click Save.
  13. Quit and restart Microsoft Access. This time log on as the user you created in Step 5.
  14. Open the MDE file created in Step 14. Note that you receive the error message mentioned in the "Symptoms" section.


REFERENCES

For more information about creating MDE files, search the Help Index for "MDE files, and then "about MDE files."


Additional query words: record s can t be read no read permissions on MsysModules2

Keywords: kbbug kberrmsg KB170696