ACC2000: Empty DBF File or Access Stops Responding When You Export to dBASE File Format (300571)



The information in this article applies to:

  • Microsoft Access 2000

This article was previously published under Q300571
Novice: Requires knowledge of the user interface on single-user computers.

This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).

SYMPTOMS

When you export to the dBASE file format, an empty .dbf file is created or Microsoft Access stops responding (hangs).

CAUSE

You may experience one of the behaviors that is mentioned in the "Symptoms" section when both of the following conditions are true:
  • The table contains a Memo field. -and-

  • The destination folder's path name is longer than 66 characters.

RESOLUTION

To prevent this behavior, do one of the following:
  • When you export to dBASE file format, select a folder with a path name that is shorter than 67 characters. -or-

  • Change the table's Memo field to a Text field.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce the Behavior

  1. Create a folder for which the full path to the folder exceeds 66 characters.
  2. Open the sample database Northwind.mdb.
  3. Click Tables under Objects, and then click the Employees table.
  4. On the File menu, click Export.
  5. In the Export Table 'Employees' To dialog box, use the Save in box to browse to the folder that you created in step 1.
  6. In the Save as type box, click dBASE 5 (*.dbf).
  7. Click Save.

    NOTE: Access may stop responding at this point.
  8. On the File menu, point to Get External Data, and then click Link Tables.
  9. In the Link dialog box, use the Look in box to browse to the folder that you created in step 1.
  10. In the Files of type box, click dBASE 5 (*.dbf).
  11. Click EMPLOYEE.DBF.
  12. Click Link, and then click Close.
  13. Open the linked EMPLOYEE table. Note that the table does not contain data.

Modification Type:MinorLast Reviewed:7/15/2004
Keywords:kbbug kbnofix KB300571