ACC: Exporting to FoxPro 3.0 Does Not Create a .CDX File

 Last reviewed: June 4, 1997
Article ID: Q162659
The information in this article applies to:
  • Microsoft Access versions 7.0, 97

SYMPTOMS

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

When you export a Microsoft Access table to a Microsoft FoxPro 3.0 file format, a FoxPro index file (*.cdx) is not created. However, a .cdx file is created when you export a Microsoft Access table that contains an index to a Microsoft FoxPro 2.0, 2.5, or 2.6 file format.

CAUSE

Microsoft Access 7.0 and 97 do not support creating indexes on Microsoft FoxPro 3.0 tables.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open the sample database Northwind.mdb.

  2. Select the Suppliers table in the Database window.

  3. On the File menu, click Save As/Export.

  4. In the Save As dialog box, click "To an External File or Database," and then click OK.

  5. In the "Save Table 'Suppliers' In" dialog box, select Microsoft FoxPro 3.0 (*.dbf) in the Save As type box, and then click Export.

  6. Start Windows Explorer or File Manager, and open the folder in which you saved the FoxPro file. Note that Microsoft Access created a Supplier.dbf file, but there is no corresponding Supplier.cdx file.

REFERENCES

For more information about exporting to Microsoft FoxPro file formats, search the Help Index for "FoxPro, exporting Access data," or ask the Microsoft Access 97 Office Assistant.

Keywords : IsmXbase kbinterop
Version : 7.0 97
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided

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