ACC1x: Using TransferDatabase to Export to Btrieve Format

Last reviewed: April 2, 1997
Article ID: Q92694
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

According to the online Help topic for the TransferDatabase action, it is not necessary to have a Database Name entry in order to export to Btrieve format. This is incorrect.

RESOLUTION

The third paragraph under "Database Name" should read:

   For Btrieve databases, enter the path and file name (FILE.DDF)
   of the Xtrieve dictionary file for the Btrieve database. If the
   path you specify does not contain an Xtrieve dictionary file,
   Microsoft Access will create a dictionary file. This is a
   required entry. If you do not know the location of an Xtrieve
   dictionary file, enter a space <using the spacebar> and
   Microsoft Access will create this file for you.

STATUS

This behavior no longer occurs in Microsoft Access version 2.0.

MORE INFORMATION

You must enter either a space or an invalid path before Microsoft Access will create a dictionary file for you. An Xtrieve dictionary file is required when exporting a table to Btrieve format.

Btrieve is manufactured by Btrieve Technologies, Inc., a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.


Keywords : kbusage McrArg
Version : 1.0 1.1
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: April 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.