Firebird
Access

Firebird / InterBase to Access Converter

Move Firebird or InterBase tables into Microsoft Access .mdb or .accdb files for reporting, Office workflows, or lightweight local databases with type-mapping review and optional sync.

Firebird → Access migration usually means copying selected Firebird or InterBase tables into a Microsoft Access .mdb or .accdb file for reporting, Office workflows, or a lightweight local database.

DBConvert handles the table-level move: it reads Firebird .fdb / .gdb files or server databases, creates Access-compatible tables, maps field types, transfers rows, and can save the job for repeatable exports. The review work is in Access file size, generated keys, BLOB/text handling, date/time values, and Firebird PSQL objects that Access cannot run.

What DBConvert does on this path: handles Firebird → Access as a repeatable desktop workflow:

  • Reads Firebird 2.5 / 3.0 / 4.0 and InterBase sources, including .fdb and .gdb database files.
  • Writes a Microsoft Access .mdb or .accdb target file.
  • Maps tables, fields, indexes, primary keys, foreign keys, and supported views with type-mapping review.
  • Saves the job as a rerunnable session; DBSync keeps Firebird and Access aligned while the Access file is still updated.

What it does not do: Firebird PSQL procedures, triggers, selectable procedures, event handlers, computed-by expressions, and application logic do not become Access forms, reports, macros, or VBA.

Which tool: DBConvert or DBSync?

DBConvert for Firebird → Access

One-time migration or repeatable exports. Use it when Access is the target file for reporting, sharing, QA samples, or a lightweight local workflow.

DBSync for Firebird ↔ Access

Staged cutover or recurring exchange. Use it when a Firebird system and Access file must keep sharing inserts, updates, and deletes for a period of time. Review synchronization concepts.

Need more context? Compare DBConvert and DBSync side by side →

How DBConvert handles the Firebird → Access differences

DBConvert handles connection, object selection, type mapping, Access file creation, row transfer, and validation. Firebird server-side code and Access application design remain separate work.

Source and target shape

DBConvert reads a Firebird file or server and writes an Access .mdb or .accdb. Access is capped at 2 GB, so large Firebird sources should be filtered or split.

Generated keys

Firebird generators, sequences, and identity columns need an Access AutoNumber or Number policy. Confirm next values before new Access inserts begin.

BLOB and long text

Firebird text BLOBs map to Access Long Text; binary BLOBs map to OLE Object / attachment-style storage policies depending on the target file format and application needs.

Charset and identifiers

Firebird character sets and quoted identifiers need an Access naming and encoding policy. Test accented text, mixed-case names, and reserved words during the first load.

Procedural code boundary

DBConvert migrates tables, fields, supported views, indexes, and foreign keys. Firebird PSQL procedures, triggers, selectable procedures, computed-by columns, event handlers, and application behavior remain outside the Access file export.

Type mapping checkpoints

Firebird Access Notes
SMALLINT / INTEGER / BIGINT Number / Large Number Large Number requires modern Access .accdb.
DECIMAL(p,s) / NUMERIC(p,s) Decimal / Number Review precision and scale before reports use the Access file.
VARCHAR / CHAR Short Text Check Access text length limits and encoding.
BLOB SUB_TYPE 1 (text) Long Text Sample long notes and Unicode content after import.
BLOB SUB_TYPE 0 (binary) OLE Object / attachment policy Validate with real files, not only row counts.
DATE / TIME / TIMESTAMP Date/Time Check blank or sentinel dates in legacy data.
BOOLEAN Yes/No Confirm true / false / unknown values if the source used nullable booleans.

Choosing the Firebird → Access route

Most projects are either a one-time Access export, a recurring reporting copy, or a temporary compatibility bridge.

Route Where it fits Where it falls short
DBConvert / DBSync You need a GUI workflow, Access file output, filters, type mapping review, saved sessions, or recurring synchronization. Firebird PSQL and Access application objects remain outside the row-copy workflow.
Access linked tables through ODBC Users only need to browse or report against live Firebird data from Access. This is not a conversion; it depends on drivers, network access, permissions, and live Firebird availability.
CSV export and Access import A few flat tables need to be moved once and relationships are not important. You lose schema metadata, constraints, type nuance, indexes, and repeatability unless you script them separately.
Custom ETL The Access file is only one output of a larger reporting or archival pipeline. You own driver setup, data shaping, Access size limits, retries, and validation.

Access target planning checklist

Lock down these choices before the final Firebird export.

File format and size

Pick .mdb or .accdb, then confirm the export fits under the Access 2 GB file cap.

Table selection

Use filters or selected tables if Access is only a reporting copy, not a full Firebird replacement.

Large values

Sample text BLOBs, binary BLOBs, Unicode text, and timestamp columns after the first import.

Validation

Compare row counts, key aggregates, relationship behavior, and report output before replacing the old export process.

Supported versions

  • Firebird 2.x, 3.x, 4.x and InterBase
  • MS Access .mdb (Jet) and .accdb (ACE) files
  • WorkGroups credentials and linked tables

Supported in this path

Source Firebird
Target Access
Firebird 2.x, 3.x, 4.x InterBase Microsoft Access .mdb Microsoft Access .accdb
Firebird

All Firebird Tools

Other directions and pairs
Access

All Access Tools

Migration & sync options

Reverse Conversion

Access to Firebird

Using Firebird to Access Tools

When launching the DBConvert or DBSync application in GUI mode, it guides you through the steps to start database migration or synchronization:

1

Connect to Firebird source database

Specify the username/password and host/port parameters if your source database requires login credentials.

Connect to Firebird source database from DBConvert

Firebird source

Point DBConvert at a Firebird .fdb / .gdb file or a Firebird 2.5 / 3.0 / 4.0 server — Firebird source settings.

2

Connect to Access destination database

Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.

Connect to Access target database from DBConvert

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.

More guides for Firebird ↔ Access

Next steps: configure, validate, run

After connecting source and target, the remaining steps are the same for every database pair:

  • Configure migration options — pick tables, fields, indices, views.
  • Issue detection — the built-in checker flags integrity problems before migration starts.
  • Execute — commit the job, monitor progress, save the session for reuse.
  • Schedule and CLI — rerun saved sessions on a schedule or from the command line.
Open the full guide

Steps 3–5, software features, command-line mode, scheduler, and system requirements.

See all features