Converting Microsoft® Access 95 and 97 Databases
Information and guidance on how to convert Access 95 and 97 databases (mdb file format) to Microsoft® Access accdb file format.
Last updated on 2021-01-26 by David Wallis.
Microsoft has not provided support for Microsoft Access 95 and 97 for years. No longer do you find tools for converting your Access 95 and 97 databases included in the latest versions of Microsoft Access.
I intend to continue to offer Access 95 and 97 conversion services for the foreseeable future — complete conversions or assistance to you as you attempt them yourself.
Access 2010, 2013, 201, 2019 and Access for Microsoft 365 Conversion Tools
Access versions 2010, 2013, 2016, 2019 and Microsoft 365 have a feature to save a database in an earlier version:
I’ve never received a request for a backwards conversion. (I can’t understand why anyone would want to do this.)
Access versions 2013, 2016, 2019 and Microsoft 365 lack tools for converting databases from the outdated mdb file format of Access 95 and 97 to their own accdb file format.
So, to get an Access 95 or 97 mdb file up to an accdb format that Access 2013, 2016, 2019 and Microsoft 365 will recognise, you need to adopt an intermediate step. That is, in either Access 2007 and 2010, open your Access 95 or 97 mdb and you’re presented with the Database Enhancements options:
Click Yes and Access will present you with a Save As dialog box in which you give your converted database a file name. You should then have a converted database that versions 2013, 2016, 2019 and Microsoft 365 of Access will allow you to open.
In my experience, Access 2010 rarely completes the conversion of an Access 95 or 97 database without some errors:
Not all errors get logged for attention as part of any conversion process. I have examples of errors coming to light only when supposedly successfully-converted databases crashed during use.
Some of these errors are due to certain objects that fail to convert. For instance tables, queries, and reports all may convert faultlessly, but a form or two may not. Macros are particular offenders.
If you plan to continue using Access 2010, or to complete the move to Access for Office 365 — Microsoft recommend conversion to the latest version — then please contact me if you need assistance in preventing errors permeating conversions from earlier versions. Or read on.
Working Around Conversion Errors
Importing Into a New Database
One way to reconstruct a database that fails a straight conversion is to start a new one and import into it the objects from the original. You’ll need to use Access 2007 or 2010 for this.
In a new database, go to the External Data tab and then click Access:
In the Get External Data - Access Database dialog box, click Browse and navigate to your old database file. Make sure you select the Import tables … option before clicking OK to commence the import.
Getting Hold of the Data Using Excel
The most precious part of your Access 95 or 97 database is likely to be the data stored in it. So if your attempts at conversion have proved unsuccessful, another approach is to use Excel to extract the data from the database tables.
You’ll need Excel 2007 or 2010, because later versions will not recognise Access 95 or 97 databases. So lay your hands on a PC with Office 2007 or Office 2010. Ordinary Office will be good enough — you don’t need Office Professional, the one that contains Access.
In an empty spreadsheet, Data → Get External Data → click From Access:
Navigate to your database file and once you’ve opened it, choose the table you want to import. Repeat the process for each table. I recommend you start a new worksheet for each table.
With your worbook saved, you can use Access 2013, 2016, 2019 or Microsoft 365 to import the contents of its worksheets.
Slow-running Converted Access Databases
Some clients have been disappointed with the speed of their databases following conversion to Access 2010, 2013, 2016, 2019 and Access for Microsoft 365.
The majority of databases I’ve been hired to convert have had design flaws that directly contributed to poor performance. In carrying over those flaws, the performance hits have been magnified by later versions of Access.
I’ve built up experience of what adjustments need to be made if your converted database suffers from this problem.
An Opportunity to Improve Usability
If now you are upgrading to Access 2013 or later, then your database must have been in use for many years. So you’ll have had time to identify improvements you would like to make and to assess the relevance of some bits that nobody uses any longer.
Also, users will have views on what would make their database more relevant to their work than it is in its current form.
A common complaint from users is that their old database appear unnecessarily scrunched up on today’s monitors.
Probably, therefore, this is the best time to mount a review with a mind to redeveloping sections of the database as part of the upgrade.
An Opportunity to Gain Business Advantage
A long-standing database — in which a lot of time and effort has been invested collecting and inputting information — may not be yielding nearly enough return on all that investment.
For example, a company created their own database for recording orders received. The database held over seven years’ worth of orders. The company approached me to learn how they might take full advantage of all this information, reporting on, for example:
- Patterns of seasonal variations in orders
- Products with high levels of returns
- Products yielding exceptional profit
- Predicted stock levels
- Products that could be dropped from the catalogue without harm to the bottom line
- Patterns of delayed delivery due to insufficient stock
- Problematic customers
- Lapsed customers with who we could re-establish contact
- Most profitable market sectors.
As part of your conversion process you might consider adding beefed up reporting to increase returns on investment in your database. Please contact me if you want someone with ideas from the outside to brainstorm the possibilities.
Help Converting Access VBA
There are changes in the Access VBA as you move up through the versions. Some of these changes are quite major ones. Some offer increased functionality that you may wish to exploit as part of a conversion upgrade.
The convert-database feature takes a stab at converting your VBA code. In my experience, conversion are very far from perfect. You might want to talk to us before you press the button or if you want Access VBA help in general.
32 and 64 bit Access
In July 2010 Access 2010 became available in both 32 and 64 bit versions.
Before September 2018, the 32 bit version was recommended by Microsoft as the default installation of Access, alongside the other 32 bit programs of Office. Nowadays the 64 bit version is their recommended default, as it is for all their Office 365 programs.
When converting your Access 95 or 97 database, you’ll need to give careful thought as the choice between 32 and 64 bit. So please read Microsoft Access: Its 32 and 64 bit Versions.
Converting Access MDE Files
If your database is in MDE file format, there are utilities advertised that claim to unlock MDEs. Once unlocked, so the claim goes, you can make changes to your MDE.
I’ve tried one unlocker program that gets mentioned a lot on the Web. In those Access 95/97 MDEs that I’ve “unlocked” using it, the majority of forms and reports will not go into design view. Furthermore, none of the VBA modules is rendered accessible.
So a conversion may be the best time to review the functionality of your database prior to offering to tender for the rewrite.
Your Support for DMW TIPS
Please support this website by making a donation to help keep it free of advertising and to help towards cost of time spent adding new content.
To make a contribution by PayPal in GBP (£ sterling) —
To make a contribution by PayPal in USD ($ US) —
If you’d like an invoice to account for your donation, let me know how much you’re donating —
Thanks, in anticipation.