ACC: Empty Table List When Attaching Btrieve Table

Last reviewed: May 7, 1997
Article ID: Q94828
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1, 2.0

SYMPTOMS

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

When you attach a Btrieve table, you select the Xtrieve dictionary file (FILE.DDF) in the Select File box. When you choose OK, Microsoft Access opens the dictionary file and displays a list of tables you can import or attach. However, the list is empty. In Microsoft Access version 2.0, you may receive the error message:

   Btrieve: Can't find file FIELD.DDF

CAUSE

You do not have the FIELD.DDF file that Microsoft Access requires to attach a Btrieve table.

RESOLUTION

Microsoft Access requires the following three .DDF files in order to attach a Btrieve table: FILE.DDF, INDEX.DDF, and FIELD.DDF. Make sure that you have all three .DDF files before you try to attach a Btrieve table.

MORE INFORMATION

When Microsoft Access cannot find the FIELD.DDF file, it creates a 6144-byte dummy FIELD.DDF file in the same directory in which FILE.DDF appears. If you find this dummy file, you know that you are missing the required FIELD.DDF file. Use Xtrieve or another third-party utility to create the required .DDF files.

Btrieve and Xtrieve are manufactured by Pervasive Software, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.


Additional query words: index blank
Keywords : IsmBtrv kb3rdparty kberrmsg
Version : 1.0 1.1 2.0
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: May 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.