Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Disk & Database›.mdb
THE FILE FIELD GUIDE
.mdb

Access Data（）

Disk & Database

MDB is a legacy Access database that may include queries, forms, reports and code. Review format generation, external links and security/authentication before migration.

What it is used for
Storage of legacy Access databases
What the file contains
Binary data
All sections, questions and sources

Content reviewed： · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

Inspect in Access

The database may include forms and other objects.

  1. Identify Access version and companion databases.
  2. Open a copy and review any request to enable active content.
  3. Inspect tables, queries, forms and linked tables.
Export required tables

Table export and application migration differ.

  1. Select the intended table/query and inspect counts.
  2. Export separately to a supported spreadsheet/text format.
  3. Compare encoding, types, dates and blanks.
Migrate to a newer format

Validate application behavior on a copy.

  1. Check supported conversion and version restrictions.
  2. Save separately to a supported target such as ACCDB.
  3. Test forms, queries, links and required workflows.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Unsupported old format: check compatible versions and staged conversion needs.
  • Missing linked tables: inspect source locations, connections and access.
  • Code failure: review libraries/architecture without disabling protections blindly.
  • Runtime cannot edit design: distinguish runtime and authoring Access.
  • Excel types differ: compare numbers, dates, blanks and identifiers.
  • Missing exported table: distinguish tables, saved queries and selected output.

MDB → ACCDB / CSV

  1. Open a copy in compatible Access and save/export the required format/data.
  2. Compare forms, reports, links and record counts before switching.
  3. Test required forms and linked tables on the migrated copy.

Legacy security/objects may not migrate directly; CSV holds table data, not the whole application.

Separate data and application objects

Inventory queries, forms, reports and links before choosing table export versus application migration.

Example: successful table viewing does not establish working forms; test required input workflows.

Source for these steps：Microsoft · Export a database object to another Access database / Microsoft · Export data to a text file / Microsoft · Convert an .accdb database to an earlier file format

Validate the migrated database

Test input, calculations and printing as well as row counts, retaining the original and external data backups.

Source for these steps：Microsoft · Export a database object to another Access database / Microsoft · Export data to a text file / Microsoft · Convert an .accdb database to an earlier file format

Related-format differences

Related-format differences
Format / methodRoleWhat to verify
MDBLegacy Access formatVersion/links
ACCDBNewer Access formatCompatibility
CSV / XLSXTabular dataApplication objects differ

Handling and security

Review macros/VBA/external connections and redact private data from public exports.

Questions and answers

Can Excel read the whole database?

Table import is different from using forms/code.

Can I rename it ACCDB?

No; use a supported conversion workflow.

Can Runtime redesign the database?

Running an application differs from design editing.

Does sending MDB include linked-table data?

Linked tables may refer elsewhere; inspect target data and delivery requirements.

Will Excel export preserve forms?

Table export does not transfer the application’s forms, macros or query behavior.

Format facts: name, steward and MIME type
Formal name
Microsoft Access database (MDB)
Steward / specification
Microsoft
MIME type
Depends on the producer or server; an extension alone does not establish a MIME type.

Primary and official sources