Help and Support
 

powered byLive Search

You receive error messages when you convert Workgroup Information (.mdw) file to Access 2002

Article ID:282357
Last Review:January 26, 2005
Revision:4.1
This article was previously published under Q282357
For a Microsoft Office Access 2003 version of this article, see 824258 (http://support.microsoft.com/kb/824258/).
Moderate: Requires basic macro, coding, and interoperability skills.

This article applies only to a Microsoft Access database (.mdb).

On This Page

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.

Back to the top

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).

Back to the top

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.

Back to the top

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:
1.Start Access 2002 but do not open a database.
2.On the Tools menu, point to Security, and then click Workgroup Administrator.
3.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.
4.On the Tools menu, point to Database Utilities, point to Convert Database, and then click To Access 2002 File Format.
5.In the Database to Convert from dialog box, browse to select the database that you want to convert, and then click Convert.
6.In the Logon dialog box, type your user name and password for the secured database, and then click OK.
7.Type a name for the converted database and click OK.
8.Click OK to acknowledge the message about sharing the database with users of earlier versions of Access.

Back to the top

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:
1.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.
2.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.
3.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.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Back to the top

MORE INFORMATION

You should not convert workgroup information files by using the Convert Database utilities in Access. There are two reasons for this: First, there have been security improvements in Microsoft Jet 4.0 workgroup information files, and to take advantage of these improvements, you must re-create the workgroup information file.

Second, even though workgroup information files are standard Jet database files, they do not contain an Access project storage for forms, reports, macros, and modules. When Access attempts to convert the file, it generates error messages because it cannot locate the Access project storage for these objects. The MSysAccessObjects table is the table that contains the Access project storage, and this table exists only in databases that have been 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 Office Assistant or the Answer Wizard, and then click Search to view the topics returned.

Back to the top

Steps to Reproduce the Problem

1.On a computer that has Access 97 installed, create a new Workgroup Information file by following these steps:
a. Click Start, click Run, type C:\Windows\System\WRKGADM.EXE in the Open box, and then click OK. (Be sure to replace this path with the correct path to your System folder on your computer, if necessary.)
b. Make a note of the path and file name of the current Workgroup Information file in the Workgroup Administrator dialog box, and then click Create.
c. In the Workgroup Owner Information dialog box, enter the data of your choice, and then click OK.
d. In the Workgroup Information File dialog box, click Browse to select a convenient folder, type the name Test97 in the File name box, and then click OK.
e. In the Confirm Workgroup Information dialog box, click OK, and then click OK to the completion notice.
f. Click Join, and then type the path and name of the original Workgroup Information file.
2.Copy the file Test97.mdw to a computer on which Access 2002 is installed.
3.Start Access 2002.
4.Open any unsecured database.
5.On the Tools menu, click Options.
6.On the Advanced tab, click Access 2002 in the Default File Format box.
7.Click OK to close the Options dialog box.
8.Close the database, but leave Access running.
9.On the Tools menu, point to Database Utilities, point to Convert Database, and then click To Access 2002 File Format.
10.In the Database to Convert From dialog box, click Workgroup Files (*.mdw) in the Files of type list, and then browse to select Test97.mdw.
11.Click Convert.
12.In the Convert Database Into dialog box, click Workgroup Files (*.mdw) in the Save as type list.
13.Type Test2002.MDW in the File Name box, and then click Save. Notice that you receive the following error message:
The Microsoft Jet database engine cannot find the input table or query 'MSysAccessObjects'. Make sure it exists and that its name is spelled correctly.

Back to the top


APPLIES TO
Microsoft Access 2002 Standard Edition

Back to the top

Keywords: 
kberrmsg kbtshoot kbconversion kbprb KB282357

Back to the top

Article Translations

 

Related Support Centers

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.