Firebird
Access

Firebird to Access Converter

Firebird tables into a new Access file for reporting or a local copy, with a job you can run again to keep it current.

Version
5.8.0
Release Date
Nov. 8, 2026
Size
122.4 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Copy Firebird tables into a Microsoft Access file for reporting, Office workflows, or a local copy. DBConvert creates the Access file, its tables, keys, and indexes, and transfers the rows directly from the Firebird server.

  • Reads a database on a local or remote Firebird server. Tested against Firebird 3 and Firebird 5, including the INT128, DECFLOAT, and time-zone types Firebird 4 introduced.
  • Writes an .accdb file, or an .mdb in Access 2000 format.
  • Runs on Windows as a desktop application.
  • The same download converts Access into Firebird.

Prepare a repeatable Access export

Connections, tables, and mappings remain available on separate screens as you prepare the job.

Connect by path or alias

Enter the Firebird server's host and the database's path on that server, or its alias, then pick the connection character set. See Firebird connection settings.

Review the types

Every column gets a proposed Access type you can change before the run. Conversions that change how a value looks, such as a time zone turned into UTC, are named in the log.

Save the job

Keep both connections, the table selection, and the options in a job. Run it again from the interface, or by name from a batch file or Task Scheduler with --run-job.

Export once, or keep the Access file current

Both modes are part of the same DBConvert application.

One-time export

The run creates the Access file and loads the selected tables. A value an Access column cannot hold is refused as a row error that names the table and the column, never stored as NULL or a rounded number, and the rows after it still load.

Synchronization

Run the job again to bring changes across. Rows are compared by key and only the differences are written, so a sync straight after an export has nothing to do. Read how keys and direction work. A second job runs the other direction.

How Firebird types map to Access

These are the defaults. Exact numbers stay Decimal, and every date and time becomes Date/Time.

Scroll sideways to see all columns.

In Firebird DBConvert default in Access What to know
NUMERIC, DECIMAL, INT128, BIGINT Decimal with the source scale. 64-bit columns get 19 digits, wider ones 28; BIGINT becomes Decimal(19,0). Access holds 28 digits. A value with more integer digits than that is refused by name.
SMALLINT, INTEGER, FLOAT, DOUBLE PRECISION Integer, Long Integer, Single, Double. Each value range fits its target.
BOOLEAN Yes/No. Access has no empty Yes/No: a NULL becomes No.
DATE, TIME, TIMESTAMP Date/Time. A TIME is stored on 30 December 1899, Access's day zero. Access dates start in the year 100; an earlier date is refused by name.
TIME / TIMESTAMP WITH TIME ZONE Date/Time holding the UTC instant. Access stores no zone. The log names each such column.
CHAR, VARCHAR, text BLOB Short Text up to 255 characters, Long Text above that and for text BLOBs. Firebird's CHAR padding is not part of the value.
Binary BLOB, CHARACTER SET OCTETS OLE Object, and Binary for OCTETS columns. Bytes are copied as bytes, including CHAR(16) OCTETS UUID keys.
DECFLOAT Short Text holding every digit. Access has no decimal floating point. The log names the column.
Identity columns AutoNumber. New Access rows continue from the last id. A plain INTEGER key stays a Long Integer key.

PSQL stays in Firebird

The export covers tables, their fields, defaults, and indexes, and the foreign keys. Stored procedures, triggers, and views are not converted; Access has no server-side code to receive them.

What the Access side needs

  • The installer adds Microsoft's 64-bit Access Database Engine if it is missing. If a 32-bit Office blocks it, Connect says so and links to Microsoft's download.
  • Room in the file: Microsoft caps an Access file at 2 GB, so select tables accordingly for a large source.
  • A database password is supported. Workgroup security (.mdw files) is not.

On the Firebird side, the server's port, 3050 by default, has to be reachable from the machine running DBConvert.

Supported versions and services

Firebird

  • Firebird 3.x, 4.x, 5.x

Access

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

How to migrate Firebird to Access

1

Setup: connect Firebird and Access

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.

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

Firebird source

Enter the Firebird server's host and the database's path on that server, or its alias, and select the connection character set. See Firebird source settings.

Access target

Write a fresh .mdb or .accdb file. Microsoft caps the file at 2 GB; pre-filter the export if the source is larger.

2

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

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

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.

Verify the copy

With Verify after the run on, the destination is checked when the copy ends: schema, totals and rows. The window shows which tables, rows and columns differ.

How Verify works

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.

Move Firebird data into Access

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

Windows Windows 10 or later · 122.4 MB