Microsoft KB Archive/824258

= You receive error messages when you convert the workgroup information (.mdw) file in Access 2003 =

Article ID: 824258

Article Last Modified on 9/27/2006

-

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.



SYMPTOMS
When 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.



CAUSE
This 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.



RESOLUTION
To 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 File

To 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:
 * 1) Start Access 2003.

Do not open any database.
 * 1) On the Tools menu, point to Security, and then click Workgroup Administrator.
 * 2) 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.
 * 3) On the Tools menu, point to Database Utilities, point to Convert Database, and then click To Access 2002 - 2003 File Format.
 * 4) In the Database to Convert from dialog box, select the database that you want to convert, and then click Convert.
 * 5) In the Logon dialog box, type the user name and the password for the security-enhanced database, and then click OK.
 * 6) In the Convert Database Into box, type a name for the converted database, and then click OK.
 * 7) 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 2003

To 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:
 * 1) 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.
 * 1) 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.
 * 1) 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.



MORE INFORMATION
You must not convert the Workgroup Information file by using the Convert Database utility in Access. There are two reasons for this:

First, there are security enhancements in Microsoft Jet 4.0 Workgroup Information files. To take advantage of these improvements, you must re-create the Workgroup Information file.

Second, although Workgroup Information files are standard Jet database files, the Workgroup Information files do not contain Access project storage for forms, for reports, for macros, and for modules. When Access tries to convert the file, Access generates error messages because Access cannot locate the Access project storage for these objects. The MSysAccessObjects table is the table that contains the Access project storage. This table exists only in databases that are opened in Access.

For more information about user-level security and workgroup files, click Microsoft Access Help on the Help menu, type user-level security in the Search for box in the Assistance pane, and then click Start searching to view the topic.

Steps to Reproduce the Problem
<ol> On a computer that is running Access 97, create a new Workgroup Information file. To create a new Workgroup Information file, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, and then click Run.</li> In the Run box, type c:\windows\system\wrkgadm.exe, and then click OK.

Note If the path of the System folder is different on your computer, you must modify the path.</li> Make a note of the path and of the file name of the current Workgroup Information file, and then click Create.

Note The path and the file name information is in the Workgroup Administrator dialog box.</li> In the Workgroup Owner Information dialog box, type the data of your choice, and then click OK.</li> In the Workgroup Information File dialog box, click Browse to select a convenient folder, type Test97 in the File name box, and then click OK.</li> In the Confirm Workgroup Information dialog box, click OK, and then click OK to finish.</li> Click Join, and then type the path and the name of the original Workgroup Information file.</li></ol> </li> Copy the Test97.mdw file to a computer that is running Access 2003.</li> Start Access 2003.</li> Open any nonsecure database.</li> On the Tools menu, click Options.</li> On the Advanced tab in the Default File Format box, select Access 2002 - 2003.</li> In the Options dialog box, click OK.

This closes the Options dialog box.</li> Close the database, but leave Access running.</li> On the Tools menu, point to Database Utilities, point to Convert Database, and then click To Access 2002 - 2003 File Format.</li> <li>In the Database to Convert From dialog box, click Workgroup Files (*.mdw) in the Files of type list, and then select the Test97.mdw file.</li> <li>Click Convert.</li> <li>In the Save as type list in the Convert Database Into dialog box, click Workgroup Files (*.mdw).</li> <li>Type Test2003.mdw in the File Name box, and then click Save.

Notice that you receive the error messages that are mentioned in the &quot;Symptoms&quot; section.</li></ol>

Additional query words: Acc2003

Keywords: kbsecurity kbconvert kberrmsg kbprb KB824258

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.