DBConvert for MS Access & MS FoxPro — Complete Migration Guide

Troubleshooting DBConvert for MS Access & MS FoxPro: Common Issues and Fixes

1. Connection failures

   • Cause: Wrong DSN/driver, incorrect file path, or insufficient permissions.
   • Fix: Verify ODBC driver installation (Access/Visual FoxPro), confirm DSN settings or direct file path, run app as administrator, and ensure source files are not opened exclusively by another process.

2. Authentication errors

   • Cause: Incorrect credentials or missing workgroup (.mdw) for older Access/FoxPro security.
   • Fix: Re-enter username/password, supply correct workgroup file, or export data to an unsecured copy before conversion.

3. Missing tables or objects after conversion

   • Cause: Unsupported object types (queries, macros, forms) or filtering rules in mapping.
   • Fix: Check conversion settings to include all objects; convert queries as tables or export query results separately; handle forms/macros manually.

4. Data truncation or incorrect field mapping

   • Cause: Field-size/type mismatches (e.g., memo vs. text, numeric precision), locale/encoding differences.
   • Fix: Review and edit field mappings before conversion, increase target field sizes, choose appropriate data types, and test with sample records.

5. Character encoding problems (garbled text)

   • Cause: Mismatched code pages between source and target (ANSI vs. UTF-8).
   • Fix: Set correct encoding options in DBConvert, convert via UTF-8 where supported, or export/import via CSV specifying encoding.

6. Slow performance or long-running conversions

   • Cause: Large dataset, network latency, or running without indexes.
   • Fix: Convert in batches, run locally (avoid network shares), disable nonessential logging, ensure indexes exist on source for faster reads, or increase buffer sizes if option available.

7. Foreign key / relationship issues

   • Cause: Relationships not recreated or referential integrity lost.
   • Fix: Enable relationship mapping in settings, or recreate keys in target DB after data transfer using the provided DDL export.

8. Duplicate or missing records

   • Cause: Incorrect primary key mapping, SELECT filters, or transaction interruptions.
   • Fix: Ensure correct primary keys are specified, review filters, rerun conversion for affected tables, and check logs for interrupted transactions.

9. Errors during schema conversion (DDL errors)

   • Cause: Target DB doesn’t support certain data types, constraints, or reserved names.
   • Fix: Adjust schema mapping rules, rename conflicting objects, or convert schema manually and import data afterward.

10. Licensing or activation problems

    • Cause: Expired license, wrong license file, or network restrictions.
    • Fix: Verify license status, reapply activation key, ensure outbound connections to activation servers are allowed (if required), or contact vendor support.

11. Unclear log messages

    • Cause: Verbose or cryptic error output.
    • Fix: Enable detailed logging in DBConvert, capture the full log, and search vendor knowledge base or support forums with exact error text.

Quick checklist before retrying a conversion:

• Backup source and target databases.
• Test conversion on a small subset.
• Confirm drivers and permissions.
• Review and adjust field/type mappings.
• Enable detailed logs and inspect errors.

If problems persist, collect: DBConvert log, sample source table schema + sample rows, exact error messages, OS and driver versions — then contact vendor support.