Why Access 97 files no longer open
Access 97 stores its data in an older version of the Jet database format. Access 2013 dropped support for that format, and every later version, including Access in Microsoft 365, has done the same. When you try to open an Access 97 .mdb file, Access reports that the database was created in an earlier version and cannot be opened.
As long as an old PC with Access 97 keeps running, nobody notices. The problem appears when that machine is replaced, Office is updated or Windows is upgraded. At that point the application often has to be rescued under time pressure, while the daily work depends on it.
Your options
There are broadly three routes. Which one fits depends on how important the application is and how long it needs to last.
- Convert the file. Access 2010 and earlier versions can still open an Access 97 database and save it in the Access 2002-2003 .mdb format or as .accdb, which current versions can open. This buys time, but the application itself stays the same.
- Move the data to a database server. The tables go to SQL Server or PostgreSQL; the Access screens stay for now and are linked to the new database.
- Modernise into a web application. Data and business rules are carried over to an application that runs in the browser, with a real database behind it.
Risks to check before converting
Access 97 applications usually contain more than tables. Before you convert, it helps to know which of these points apply to yours:
None of these is a reason not to migrate, but each one affects the effort and the best approach. A conversion alone is often a sensible first step; it rarely solves the underlying issues of one file on a network drive, no personal accounts and code that only one person understands.
- VBA code that relies on old libraries such as DAO 3.51, or on Windows API calls that need changes for 64-bit Office, the default since Office 2019/365
- ActiveX controls, such as the old calendar control, that no longer exist in recent Office versions
- User-level security with a workgroup file (.mdw), which the .accdb format no longer supports
- Compiled .mde files: these cannot be converted, you need the original .mdb with the source code
- Linked tables that point to other files, drive letters or servers that may no longer exist
How the free scan helps
AccessDB Rescue reads Access 97 files directly, so you do not need an old version of Access to see what is inside. The scan lists tables and record counts, queries, forms, reports, macros and VBA modules, and flags points of attention such as Windows API calls, linked files and lookup fields.
That gives you a factual basis for the decision: is a conversion enough for now, or is this the moment to modernise? You see the result straight away, and you can discuss it with us without obligation.
Frequently asked questions
Can Access in Microsoft 365 open an Access 97 database?
No. Since Access 2013, Access 97 files can no longer be opened or converted in Access. For a conversion you need Access 2010 or an older version, or a different route such as moving the data to a database server.
Does a conversion keep my forms and VBA code?
Usually, but not always without changes. Code that uses old libraries, ActiveX controls or Windows API calls often needs adjustments, and user-level security is lost when you convert to .accdb.
I only have an .mde file. What now?
An .mde contains compiled code without the source and cannot be converted to a newer version. Look for the original .mdb first. The scan can still read the tables, queries and structure of an .mde, but not its VBA source code.
Is my data safe during the scan?
Yes. The file is read by your own browser on your own computer. Only a summary with counts goes to our server, never your data, object names or the file itself.
Find out what is inside your Access 97 database before you decide. The free scan runs in your browser and your file is never uploaded. Then talk to us, in English or Dutch, about the route that fits.
Start the free scan