DBF to Access Troubleshooting

While working with DBF-to-Access converter you may encounter unexpected behavior or result. Use the following information to solve some common problems and get the result you want. This summary is organized as a list of problem-resolution pairs. Each problem description starts with "P:" and each resolution - with "R:".

P: I cannot uninstall DBF-to-Access.
R: If you need to remove DBF-to-Access product from your computer, you can use "Add or Remove Programs" option in the Windows Control Panel.

P: National symbols like á, â, ã, ç, é, î, ï, ô, ò, õ, ú, ù and others are not converted properly.
R: DBF-to-Access uses the code page given in header of DBF file to interpret text fields of the tables. However, sometimes DBF file stores incorrect value of code page. For such situations DBF-to-Access allows users to specify code page that will be used to interpret text fields instead of the built-in one. You can do this via "Use Encoding" combo box on "Step 3 of 5" wizard page.

P: Indexes are missing in the resulting MS Access database.
R: Current version of DBF-to-Access does not convert indexes.

P: Some table names and/or field names in the resulting MS Access database differ from the original.
R: DBF and MS Access accept different sets of characters for table names and field names. When DBF-to-Access converts a name containing prohibited characters it replaces them with '_' in the destination database.

P: I see the error message "$filename$: Memo field not found"
R: In FoxPro/DBase format data of memo fields is stores in separate file. It is expected that the corresponding memo file is in the same folder as .dbf file and has the same name with one of the following extensions: .dbt, .fpt, .smt. Make sure there is the appropriate memo file in the same folder where .dbf file is located. Copy it from another folder if necessary.

If you came across some other kind of problem while using DBF-to-Access converter, please contact our support service.