Access
FoxPro

Access to FoxPro Converter

Access tables and rows into files Visual FoxPro opens, with saved jobs you can run again.

Version
5.6.0
Release Date
Nov. 3, 2026
Size
130.5 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Export Access tables into FoxPro files. DBConvert writes the tables, memo files, and indexes itself; Visual FoxPro opens the result.

  • Reads an Access .accdb or .mdb file, with its database password. The 64-bit Microsoft Access Database Engine is required.
  • Writes a Visual FoxPro .dbc database (created when it is missing) or a folder of free tables.
  • Nothing to install for FoxPro: no Visual FoxPro OLE DB driver, no Visual FoxPro. Runs on Windows as a desktop application.
  • One licence key covers the other FoxPro pairs, such as FoxPro to SQL Server.

What it writes

Codepage of new tables

Set Codepage of new tables in the destination settings. 1252 is the default.

A .dbc or a folder

Write into a .dbc database, created when it is missing, or into a folder of free tables.

Files Visual FoxPro opens

The application writes the .dbf, .fpt, .cdx, and .dbc files itself.

A job keeps both connections, the table selection, and the options. Run it again from the application, or by name from Task Scheduler with --run-job.

Where it refuses

  • Text the chosen codepage cannot hold is refused, not written as ?.
  • An index tag other than plain fields, STR, DTOS, or LOWER blocks writing into that table.
  • A FoxPro table is capped at 2 GB.

Supported versions and services

Access

  • MS Access .accdb, and .mdb in Access 2000 format or later
  • Database password; the 64-bit Microsoft Access Database Engine is required

FoxPro

  • Visual FoxPro .dbc databases and folders of free tables
  • Plain dBase III and IV files read too
  • Nothing to install for FoxPro: the application reads and writes the files itself

How to migrate Access to FoxPro

1

Setup: connect Access and FoxPro

Pick Convert or Sync, then choose the source and destination connections side by side on one screen. A connection is saved once and reused by every job.

The Setup step in DBConvert: the mode, the Access source and FoxPro destination side by side, and the job name

Sync keeps an existing FoxPro database up to date with Access: each run carries only the inserts, updates and deletes since the last one.

The Setup step in Sync mode for Access to FoxPro: how changes are detected and the direction

Access source

Select the source .mdb or .accdb file and enter its database password if it has one. Reading it needs the 64-bit Microsoft Access Database Engine.

Look inside the Access file first

To see what an .mdb or .accdb file holds before converting it, open it in the free MDB and ACCDB Viewer: tables with their Access types, relationships as an ER diagram, saved queries and read-only SQL, in the browser, with no upload and no Access installed.

Open the MDB viewer · VS Code extension

FoxPro target

Write to a .dbc database (created when it is missing) or a folder of free tables. Choose the Codepage of new tables; 1252 is the default.

2

Tables & mapping: see every FoxPro type before a row moves

Pick the tables, then open one: each Access column shows the FoxPro type it becomes. Change a type or a name in place; the line at the bottom names anything that would fail.

Tables and mapping for Access to FoxPro: the table list and one table's columns with their FoxPro types
3

Execution: start it, and the job is saved

Review what the run will do, start it, and read the log as it goes. The job stays in the list to run again or put on a schedule.

A finished Access to FoxPro conversion: the summary and the operation log

Every option, in the guide

Naming rules, table options, row filters, scheduling and the command line work the same for every database pair, so they live in one place.

More guides for Access ↔ FoxPro

Move Access data into FoxPro

Download the current build and run the first job against your own database.

Windows Windows 10 or later · 130.5 MB