ACC: Error When Opening Table in Design View

Last reviewed: May 23, 1997
Article ID: Q92671
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1, 2.0, 7.0, 97

SUMMARY

Novice: Requires knowledge of the user interface on single-user computers.

When you try to open a table in Design view, you may receive the following error message, depending on your version of Microsoft Access.

   In Microsoft Access 97 and Microsoft Access version 7.0:

      You can't open the table <table name> for modification.

   In Microsoft Access version 2.0:

      Can't switch to Datasheet view and can't return to Design view.

   In Microsoft Access version 1.x:

      Unable to recover from attempt to switch view. Window
      will be closed.

Microsoft Access then returns focus to the Database window.

MORE INFORMATION

This error message occurs only in rare situations. It is an informational message only, not a program error.

Steps to Reproduce Behavior in Microsoft Access 7.0 and 97

  1. Two users (User A and User B) both open the sample database Northwind.mdb, non-exclusively.

  2. Both users open the Categories table in Datasheet view.

  3. Both users simultaneously switch to Design view. User A succeeds, but User B receives the following error message:

          You can't open the table <table name> for modification.
    

  4. User B tries to reopen the table in Datasheet view. The table will be opened in Design view as Read-Only without any type of message.

  5. Microsoft Access returns User B's focus to the Database window. User B will be able to make changes to the design of the table but will be unable to save them. The Save option on the File menu will be dimmed.

Steps to Reproduce Behavior in Microsoft Access version 1.x or 2.0

  1. Two users (User A and User B) both open the sample database NWIND.MDB, non-exclusively.

  2. Both users open the Categories table in Datasheet view.

  3. Both users simultaneously switch to Design view. User A succeeds, but User B receives the following error message.

    In Microsoft Access version 1.x:

          Table is in use, cannot lock by user '<user B's logon name>'
          on machine <user B's machine name>'.
    

    In Microsoft Access version 2.0:

          Can't open table 'Categories' for modification. Open it read only?
    

  4. User B tries to reopen the table in Datasheet view and receives the following error message:

          Couldn't lock table. Table 'Categories' is exclusively
          locked by user '<user A's logon name>' on machine '<user
          A's machine name>'.
    

  5. User B is returned to the Database window with the following error message.

    In Microsoft Access version 1.x:

          Unable to recover from attempt to switch view. Window
          will be closed.
    

    In Microsoft Access version 2.0:

          Can't switch to Datasheet view and can't return to Design view.
    

  6. Microsoft Access returns User B's focus to the Database window.

When in Datasheet view (step 3), both users have the table open, non- exclusively. When they try to switch to Design view, they are actually closing the table and attempting to re-open it, exclusively.

In the example above, User A succeeds and User B fails. When User B then tries to reopen the table (non-exclusively) in Datasheet view, User A already has the table open exclusively.

The error message in step 5 in an informational message designed to let User B know that Microsoft Access is unable to open the table in either Datasheet or Design view.


Keywords : kberrmsg kbusage TblDsign
Version : 1.0 1.1 2.0 7.0 97
Platform : WINDOWS
Hardware : X86
Issue type : kbinfo


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.