ACC: Adding a FoxPro Index from a Read-Only Drive Causes Error

Last reviewed: November 13, 1997
Article ID: Q153718
The information in this article applies to:
  • Microsoft Access version 7.0, 97

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you try to link a Microsoft FoxPro database with an index from a read-only drive, you may receive the following error message:

   Microsoft Access can't create, open, or write to the index file
   <filename>, the information (.inf) file it uses to keep track of dBASE
   indexes.

CAUSE

You must have read/write permissions for the drive which contains the index file so that Microsoft Access can create the .inf file.

RESOLUTION

You can use one of the following methods to work around this behavior.

Method 1

Place the FoxPro index file on a drive where you have read/write permissions.

Method 2

Link to the FoxPro file without specifying any indices.

Method 3

Place the information (.inf) file on the read-only drive along with the index file and the .dbf file.

MORE INFORMATION

Microsoft Access version 7.0 Help incorrectly states the following:

   If your FoxPro or dBASE tables are stored on a read-only drive or CD-
   ROM, Microsoft Access can't create an .inf file in the same folder as
   the .dbf files. To link a table on a read-only drive, you must specify
   the path where you want Microsoft Access to create the .inf file in the
   Windows Registry.

   Start the Registry Editor and navigate to the
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.0 key of the registry.

However, modifying this registry key does not work. Microsoft Access will ignore the registry entry and still try to create the .inf file on the same drive as the indexes.

NOTE: The Microsoft Access 97 Help Index does not contain this message.

REFERENCES

For more information about linking FoxPro files, search the Help Index for "importing data" and view the available topics, or ask the Microsoft Access 97 Office Assistant.

Keywords          : IsmXbase kb3rdparty kberrmsg
Version           : 7.0 97
Platform          : WINDOWS
Hardware          : x86
Issue type        : kbdocerr


================================================================================


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