ACC1x: Error When Opening Attached Table in Shared .MDB File 1.x

Last reviewed: June 6, 1997
Article ID: Q99936
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

When you attempt to open an attached table in a shared .MDB file, one of the following error messages appears:

  • Couldn't find file "<drive>:\<path>\<filename>"
  • "<Drive>:\<path>\<filename>" isn't a valid path
  • Couldn't open file "<drive>:\<path>\<filename>"

CAUSE

The path to an attached table is hard-coded in the table's properties. For a shared .MDB file, this path is very likely invalid.

RESOLUTION

To work around this problem, either change the path to the attached file so that it is valid, or import the data instead of attaching the table.

To verify and correct the path for an attached table, use the following procedure:

  1. Open the table in Design view.

  2. From the View menu, choose Table Properties. The Description property contains the path to the attached table.

  3. Place the .MDB file and its attached tables on a share on a dedicated server.

  4. Use one of the following two naming conventions:

        - Choose a drive letter (for example, "u:") and make sure all
          users connect to the share using that drive letter. Use the
          same drive letter for the attached tables.
    

          -or-
    

        - Use the universal naming convention (UNC) for the attached
          tables (for example, \\<server>\<share>\<filename>).
    

          NOTE: To attach a database using UNC, specify the UNC name and the
          database name where you normally would specify the drive and database
          names. For example, instead of logging on to the network drive,
          typing the database name, and choosing Attach Table from the File
          menu, you need only enter the UNC name and the database name in the
          Attach dialog box, as follows:
    

             \\MYSERVER\PUBLIC\MYDB.MDB
    
    

MORE INFORMATION

If the .MDB file is placed on a non-dedicated server that does not allow redirecting to itself (for example, Microsoft Windows for Workgroups), you must maintain two separate .MDB files, one to share with other workstations and one for your local computer.

Maintaining two separate copies of the .MDB file is necessary because Windows for Workgroups does not allow a server to redirect to itself. For example, if the server name is SERVERNM, the SERVERNM computer cannot use the path \\SERVERNM\SHARE to access a file from its own hard disk.

If the .MDB file is placed on a non-dedicated server that does allow redirecting to itself (for example, Microsoft Windows NT), you only need to maintain one .MDB file.

REFERENCES

Microsoft Access "User's Guide," version 1.0, pages 69-72


Additional query words: attach multiuser
Keywords : IntpOthr IsmIea kbinterop
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : kbworkaround


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: June 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.