ACC2: "No Permission for DBSTRUCT.MDB" Error Message
ID: Q120580
|
The information in this article applies to:
SYMPTOMS
Advanced: Requires expert coding, interoperability, and multiuser skills.
After you log on to Microsoft Access as any user other than the Admin user,
you receive the following error message when you try to open the sample
database DBSTRUCT.MDB:
No permission for '<path>\DBSTRUCT.MDB'
CAUSE
Only the Admin user has Open/Run permission on the DBSTRUCT database.
Neither the Admins group nor the Users group has Open/Run permission on
the database.
RESOLUTION
You can use the DBSTRUCT database by logging on to Microsoft Access using a
new, unsecured system database (or SYSTEM.MDA file), or you can modify the
DBSTRUCT database's permissions so that other users can open it. Both of
these methods are demonstrated below.
How to Use a New, Unsecured System Database
- Quit Microsoft Access if it is running, and then make a backup copy
of the SYSTEM.MDA file. Name the backup copy of the file SYSTEM.BAK.
- Double-click the MS Access Workgroup Administrator icon in your
Microsoft Access program group. (NOTE: This icon may be in another
group, such as the Microsoft Office program group.)
- In the Workgroup Administrator dialog box, choose the Create button to
create a new system database.
- In the Workgroup Owner Information dialog box, type appropriate
information in the Name, Organization, and Workgroup ID boxes, and
then choose the OK button.
- In the Workgroup System Database dialog box, enter a path and unique
name for the new system database file in the Database box, and then
choose OK. For example, enter:
C:\ACCESS\UNSECURE.MDA
NOTE: Do not use the same name as your secure system database file
because Microsoft Access will attempt to overwrite the file when
it creates the new file. Also, the path in the example above is for
illustrative purposes only; you should use the correct path for your
Microsoft Access installation.
- In the Confirm Workgroup Information dialog box, choose OK. When
you receive a message stating that the new system database was
created, choose OK.
- Choose the Exit button to quit the Workgroup Administrator.
- Start Microsoft Access. You should not receive a Logon dialog box,
which means that you are logging on to Microsoft Access as the default
Admin user. Since the Admin user has Open/Run permission on the
DBSTRUCT database, you should now be able to open the database.
How to Modify Permissions on the DBSTRUCT Database
- Start Microsoft Access and log on as the Admin user.
- Open the sample database DBSTRUCT.MDB.
- From the Security menu, choose Permissions.
- In the Object Type box, select Database.
- Select the Groups option button, and then select the Users group in
the User/Group Name box.
- In the Permissions group, select the Open/Run check box, and then
choose the Assign button.
- In the User/Group Name box, select the Admins group.
- In the Permissions group, select the Open/Run check box, and then
choose the Assign button.
- Choose the Close button, and then quit Microsoft Access.
- Restart Microsoft Access and log on as you normally do. You should
now be able to open the DBSTRUCT database.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Access version
2.0. We are researching this problem and will post new information here in
the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONSteps to Reproduce Problem
- In an unsecured Microsoft Access system, create a new user named USER1
and add the user to the Admins group.
- Assign a password to the default Admin user so that you will receive
a Logon dialog box when you restart Microsoft Access.
- Quit and then restart Microsoft Access. Log on to Microsoft Access as
USER1.
- Try to open the DBSTRUCT database. Since USER1 does not have Open/Run
permission on the database, you will receive the error message stated
above.
REFERENCES
Microsoft Access "Building Applications," version 2.0, Chapter 14,
"Securing Your Application," pages 313-344
Additional query words:
security login
Keywords : kberrmsg kbusage ScrtPerm
Version : 2.0
Platform : WINDOWS
Issue type : kbbug
|