ACC97: "File Already in Use" Error Opening Linked Table on Read-Only Source After SR-2 Update Applied

When you run Microsoft Access Service Release 2 (SR-2) on Microsoft Windows NT, and you try to open a linked table that is in another Access database, you may receive the following error message: After you click OK, you receive the following error message:

The database to which you are linking is on a read-only source.

To prevent this problem, you can do one of the following:

• If possible, grant the user Write permission to the share.
  
  -or-
  
  
• Install Microsoft Jet 3.51 Service Pack 2 on the client Windows NT machine.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Jet 3.51 Service Pack 2.

For additional information about Microsoft Jet 3.51 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

Steps to Reproduce Behavior

1. Make a copy of the sample database Northwind.mdb and place it on a share that is read-only or to which you at least do not have Write permission.
2. Install Microsoft Access Service Release 2 (SR-2) on Windows NT 4.0.
   
   NOTE: This cannot be the same machine on which you have the read-only share.
3. Start Microsoft Access and create a new database.
4. On the File menu, point to Get External Data, and click Link Tables. In the Link dialog box, under Files of type, make sure that Microsoft Access is selected. Locate the file that you created in step 1, and click Link.
5. In the Link Tables dialog box, select any table and click OK. You see the new linked table in the Database window.
6. Double-click the new linked table to open it.

Note that you receive the error message mentioned in the "Symptoms" section of this article.

For more information about linking tables, search the Help Index for "Linked Tables," or ask the Microsoft Access 97 Office Assistant.

For additional information about read-only databases and .ldb files, please see the following article in the Microsoft Knowledge Base: