You receive error messages when you convert Workgroup Information (.mdw) file to Access 2002 (282357)
The information in this article applies to:
This article was previously published under Q282357 For a Microsoft Office Access 2003 version of this
article, see
824258. Moderate: Requires basic macro,
coding, and interoperability skills. This article applies only to a
Microsoft Access database (.mdb). SYMPTOMS When you are using the Convert Database utility to convert
a workgroup information file (.mdw file) that was created in Microsoft Access
95 or Microsoft Access 97 to Microsoft Access 2002, you 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 query
'MSysAccessObjects'. Make sure it exists and that its name is spelled
correctly. However, you are able to join the workgroup defined by
the new .mdw file in the normal way. CAUSE This behavior occurs because the Convert Database utility
is unable to find all the components in the Workgroup Information file that are
contained in a standard Access database file (.mdb file). RESOLUTION To resolve this issue, use either of the following methods:
- Join the original workgroup information file without
converting it.
-or- - Create a new workgroup information file in Access
2002.
If you convert a secured Access 97 database to Access 2002
format, you can either use the the original workgroup information file or
create a new workgroup information file in Access 2002 and have users join the
new workgroup. When you are upgrading from Access 95 or 97, you must
convert your secured database, but you have a choice regarding the workgroup
information file. You can use the existing workgroup information file with
Access 2002, or you can create an entirely new workgroup information file. If
you choose to create a new file, which offers some security improvements, you
will need to re-enter all the details of the workgroup information file, user
accounts, and passwords. Method 1: Join the Original Workgroup Information File To convert a secured Access 95 or 97 database and continue using
the original workgroup information file, follow these steps:
- Start Access 2002 but do not open a database.
- On the Tools menu, point to Security, and then click Workgroup Administrator.
- In the Workgroup Administrator dialog box, click Join. Browse to select the workgroup information file that controls
the secured 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 File
Format.
- In the Database to Convert from dialog
box, browse to select the database that you want to convert, and then click Convert.
- In the Logon dialog box, type your user name and password for the secured
database, and then click OK.
- Type a name for the converted database and click OK.
- Click OK to acknowledge the message about sharing the database with users
of earlier versions of Access.
Method 2: Create a New Workgroup Information File To take advantage of security and performance improvements, you
can re-create the workgroup information file by following these steps:
- Create a new workgroup information file, making sure to
enter the exact, case-sensitive name, company name, and workgroup ID that were
used to create the original file. Failure to re-enter the exact entries that
were used to create the original file results in an Admins group that is
incompatible with the Admins group in the original workgroup file.
- Re-create any group accounts, making sure to enter the
exact, case-sensitive group name and personal ID (PID) for each group. Failure
to enter the exact entries used to create the original group accounts results
in group accounts that are incompatible with those from the original workgroup
file.
- Re-create each user account, making sure to enter the
exact, case-sensitive user name and PID for each user. Once again, failure to
enter the exact entries used to create the original user accounts results in
user accounts that are incompatible with those from the original workgroup
file.
STATUSMicrosoft
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: | 1/26/2005 |
---|
Keywords: | kbconversion kbtshoot kberrmsg kbprb KB282357 |
---|
|