The DBF (Database File) is the background file that stores the data in the dBase databases. This data can be exported to several other applications for different kinds of purposes. For example, you can export a DBF file containing list of contacts and their related details into MS Outlook. However, at times some issues crop up while you are performing the import. Most of them appear due to DBF file corruption. You should try to find out the exact cause of this problem and recover DBF file. If you are unable to do so, then you should use DBF repair software to repair DBF file.
Let us assume a related scenario in which you are trying to import a DBF file in MS Outlook 2000. The DBF import fails and you receive the following error message in the process:
"An error has occurred in the dBase translator while getting the contents of a file system.
The file "\.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."
Cause:
One of the causes of this problem is due to the bugs in the current version of MS FoxPro/dBase.
Due to the bugs in the application, Outlook fails to read a value that is greater than 99 years in the DBF 'Last Modified Date' field. Some applications that create DBF reset the numeric value to 0 once it crosses 99 while some continue beyond 99. The definition of the DBF file format is ambiguous enough to allow such confusion. Usually MS Office programs accommodate such bugs by increasing the count beyond 99, but this is not followed by MS FoxPro and dBase.
Resolution:
To resolve this problem, you should perform the following methods:
- Apply hotfix to cover up for the bugs: You should download and install the Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a) hotfix. This would solve the 'Last Modified Data' field problem.
- Use alternative file format: You should try to import the DBF file in another platform such as CSV (Comma Separated Values), MS Excel (.XLS), MS Access (.MDB), etc.
If the issue is still not resolved, that means the DBF is corrupt. In such cases, you should use a third-party DBF file repair software to repair DBF file. These read-only DBF recovery tools are very safe to use and do not overwrite the existing database file while scanning it.
The best DBF repair software, which repairs DBF created in dBase III-V versions for MS Visual FoxPro 6.0 to 9.0 versions, is Stellar Phoenix DBF Recovery. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this do-it-yourself software recovers DBF objects including table name, column name, column data type, etc.
Deixe o seu comentario
Post a Comment