Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/252706

From BetaArchive Wiki
Knowledge Base

Article ID: 252706

Article Last Modified on 9/23/2005


  • Microsoft Outlook 98 Standard Edition

This article was previously published under Q252706


When you try to import a dBase file (.dbf) into Outlook, the import fails and you may receive the following error message:

An error has occurred in the dBase translator while getting the contents of a file system.

The file "<path>\<file name>.dbf" was not recognized. The dBase translator was unable to recognize this file. It could be the wrong file, a version of the file type which is not supported by this translator, or the file might be corrupt.


A value greater than 99 for the year in the file's Last Modified Date field is not properly read. The year can be represented as a number between 0 and 255. Some software that creates .dbf files reset to 0 after 99, and others continue beyond 99. The original file format definition allowed some ambiguity, so either interpretation is common. Microsoft Office programs generally continue incrementing the year beyond 99, but Microsoft FoxPro and some versions of dBase do not.


A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

   Date      Version              Size    File name
   3/8/2000 001033  94,208  Odbc.sam


You can work around this problem by using an alternative file format for the import, such as comma separated values (CSV), Microsoft Excel (.xls), or Microsoft Access (.mdb).


Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. Exporting to a dBase file from Outlook works without error.


Additional query words: 98 1999 y2k

Keywords: kbbug kbqfe kbpending kbhotfixserver KB252706