You receive error messages when you convert the workgroup information (.mdw) file in Access 2003 (824258)
The information in this article applies to:
- Microsoft Office Access 2003
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access database (.mdb).
For a Microsoft Access 97 version of this article, see 301869.
For a Microsoft Access 2002 version of this article,
see
282357. SYMPTOMSWhen you use the Convert Database utility to convert a
Workgroup Information (.mdw) file that was created in Microsoft Access 95 or
in Microsoft Access 97, and you perform this conversion in Microsoft Office Access 2003 by using the To Access 2002 - 2003 File Format conversion feature, you may receive
the following error messages: Record(s) cannot be read; no read permission on
'MSysObjects'. Record(s) cannot be read; no read permission on
'MSysACEs'. The Microsoft Jet database engine cannot find the input
table or the query 'MSysAccessObjects'. Make sure it exists and that its name
is spelled correctly.
However, you can join the
workgroup that is defined by the new .mdw file. CAUSEThis problem occurs because the Convert Database utility
cannot find all the components in the Workgroup Information file that are
contained in a standard Access database (.mdb) file. RESOLUTIONTo resolve this problem, use one of the following methods:
- Join the original workgroup information file without
converting the original workgroup information file.
- Create a new Workgroup Information file in Access 2003.
If you convert a security-enhanced Access
97 database to Access 2003 format, you can either use the original
Workgroup Information file, or you can create a new Workgroup Information file
in Access 2003, and then users can join the new workgroup. When you
upgrade from Access 95 or from Access 97 to later versions of Access, you must
convert your security-enhanced database.
However, you have a choice about how you handle the Workgroup Information file.
You can use the existing Workgroup Information file with Access 2003, or you
can create a completely new Workgroup Information file. If you want to create
a new file that offers possible security enhancements,
you must re-enter all the details of the Workgroup Information file, the user
accounts, and the passwords. Join the Original Workgroup Information File Without Converting the Original Workgroup Information FileTo
convert a security-enhanced
Access 95 database or a security-enhanced Access 97 database, and then continue to use the
original Workgroup Information file, follow these steps:
- Start Access 2003.
Do not open any database. - On the Tools menu, point to
Security, and then click Workgroup
Administrator.
- In the Workgroup Administrator dialog
box, click Join. Select the Workgroup Information file that
controls the security-enhanced database
that you want to convert. Click Open, and then click
OK to join the workgroup.
- On the Tools menu, point to
Database Utilities, point to Convert
Database, and then click To Access 2002 - 2003 File
Format.
- In the Database to Convert from dialog
box, select the database that you want to convert, and then click
Convert.
- In the Logon dialog box, type the
user name and the password for the security-enhanced database,
and then click OK.
- In the Convert Database Into box, type
a name for the converted database, and then click OK.
- Click OK to acknowledge the message about
sharing the database with users of earlier versions of Access.
Create a New Workgroup Information File in Access 2003To take advantage of security enhancements
and performance improvements, you can re-create the Workgroup Information file.
To re-create the Workgroup Information file, follow these steps:
- Create a new Workgroup Information file.
Make sure
to type the exact, case-sensitive name, the company name, and the workgroup ID
that were used to create the original file. If you do not type the exact
entries that were used to create the original file, the new Admin group may be
incompatible with the Admin group in the original workgroup file.
- Re-create any group accounts.
Make sure to type the
exact, case-sensitive group name and the personal ID (PID) for each group. If
you do not type the exact entries that were used to create the original group
accounts, the new group accounts may be incompatible with the group accounts
from the original workgroup file. - Re-create each user account.
Make sure to type the
exact, case-sensitive user name and the PID for each user. If you do not type
the exact entries that were used to create the original user accounts, the new
user accounts may be incompatible with the user accounts from the original
workgroup file.
STATUS Microsoft has confirmed that this is a
problem in the Microsoft products that are listed at the beginning of this
article.
Modification Type: | Minor | Last Reviewed: | 9/27/2006 |
---|
Keywords: | kbSecurity kbconvert kberrmsg kbprb KB824258 kbAudDeveloper |
---|
|