Convert FDB to MDB

Organizations need this conversion when data in a Firebird application must be opened or maintained in Microsoft Access, which uses MDB for its older desktop database format. The process is a database migration, not a filename change, because Firebird and Access store tables, queries, relationships, and program logic differently.

What the FDB format is

.fdb is the usual database-file extension for Firebird, an open-source relational database system. Firebird applications use FDB files for tables, indexes, views, stored procedures, triggers, generators, and other database objects.

FDB files are used by desktop, embedded, and client/server applications. A file copied from a server may not open by itself: the migration can require the matching Firebird server or client library, database credentials, character set, and a valid local or network path. A Firebird backup normally uses a different extension, such as .fbk, and must be restored before conversion.

What the MDB format is

.mdb is the legacy Microsoft Access format associated with Access 2000–2003 and the Jet 4 database engine. It supports desktop tables, queries, forms, reports, indexes, and small multiuser applications, and remains useful when a receiving program accepts only legacy Access databases.

Current Access releases can open and create MDB files, but their default format is usually ACCDB. Select the Access 2002–2003 format when the output must specifically be .mdb. An MDB database has a maximum size of approximately 2 GB, including its objects and data.

Convert with a database migration utility

Full Convert Enterprise is a suitable desktop option when its current release supports the Firebird version and Access target required. It connects to Firebird, creates an Access database, transfers table data, and can migrate selected schema objects; object support varies by source feature and product edition.

1. Make a verified copy or backup of the FDB, and stop applications that write to it during migration.
2. Install the Firebird client or server components required to open the source. Test the FDB with the correct Firebird version, database path, credentials, and character set.
3. In Full Convert, create a project with Source: Firebird and Target: Microsoft Access. Enter the local file or server connection details.
4. Set the output filename to an .mdb path and choose the Access 2002–2003 format if the utility offers both MDB and ACCDB targets.
5. Review type mappings before running the job. Check Boolean fields, timestamps, Unicode text, decimal precision, BLOBs, generator-backed identifiers, NULL values, and text lengths.
6. Run the migration, then compare source and target table counts, row counts, primary keys, representative values, NULL handling, indexes, and relationships. Test the resulting MDB in the version of Access or other software that will use it.

Transfer tables through Firebird ODBC

For a smaller or selective migration, the Firebird ODBC driver and Microsoft Access can transfer relational table data without a separate conversion application.

1. Install the Firebird ODBC driver from the Firebird project and create a system or user DSN containing the correct server, database path, credentials, and character set.
2. Create a blank database in Access using Blank database and select the Access 2002–2003 format so the file is saved as .mdb.
3. In Access, choose External Data → New Data Source → From Other Sources → ODBC Database, select the Firebird DSN, and choose Import the source data into a new table in the current database.
4. Import the required tables. Recreate primary keys, indexes, relationships, queries, forms, reports, and validation rules in Access, then test the imported data.

ODBC import is primarily a table-data operation. It does not automatically reproduce Firebird stored procedures, triggers, generators, roles, permissions, selectable procedures, or application code. Views may need to be imported as tables or rewritten as Access queries.

Compatibility and quality limits

Do not rename .fdb to .mdb. The extensions identify different internal database engines and file structures; renaming does not convert anything.

Firebird domains, computed columns, generators, stored procedures, triggers, roles, and selectable procedures have no direct one-to-one equivalents in Jet. Replace them with Access tables, saved queries, validation rules, macros, or VBA as appropriate. Review every automatically generated expression and key definition.

Pay particular attention to large BLOBs, Unicode text, time-zone-related values, high-precision decimals, Boolean fields, and Firebird identifiers that conflict with Access reserved words or naming restrictions. Confirm that the converted database remains below the MDB size limit; split or archive data when necessary.

There is no generally reliable online converter to recommend for an FDB-to-MDB migration. A Firebird database may require a live server connection rather than a simple upload, and sending database contents or credentials to an unknown web service creates privacy and security risks. Use an offline migration utility or the Firebird ODBC workflow for production data.