

I recommend you start a new worksheet for each table. Navigate to your database file and once you’ve opened it, choose the table you want to import. In an empty spreadsheet, Data → Get External Data → click From Access: Ordinary Office will be good enough - you don’t need Office Professional, the one that contains Access.
#Access runtime 2010 removal tool Pc#
So lay your hands on a PC with Office 2007 or Office 2010. You’ll need Excel 2007 or 2010, because later versions will not recognise Access 95 or 97 databases. So if your attempts at conversion have proved unsuccessful, another approach is to use Excel to extract the data from the database tables. The most precious part of your Access 95 or 97 database is likely to be the data stored in it. Make sure you select the Import tables … option before clicking OK to commence the import. In the Get External Data - Access Database dialog box, click Browse and navigate to your old database file. In a new database, go to the External Data tab and then click Access: You’ll need to use Access 2007 or 2010 for this. 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. Working Around Conversion Errors Importing Into a New Database 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 call +44 (0)1732 833085 or email if you need assistance in preventing errors permeating conversions from earlier versions. For instance tables, queries, and reports all may convert faultlessly, but a form or two may not. Some of these errors are due to certain objects that fail to convert. I have examples of errors coming to light only when supposedly successfully-converted databases crashed during use.

Not all errors get logged for attention as part of any conversion process. In my experience, Access 2010 rarely completes the conversion of an Access 95 or 97 database without some errors: You should then have a converted database that versions 2013, 2016, 2019 and Microsoft 365 of Access will allow you to open. That is, in either Access 20, open your Access 95 or 97 mdb and you’re presented with the Database Enhancements options:Ĭlick Yes and Access will present you with a Save As dialog box in which you give your converted database a file name. 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. mdb file format of Access 95 and 97 to their own. (I can’t understand why anyone would want to do this.)Īccess versions 2013, 2016, 2019 and Microsoft 365 lack tools for converting databases from the outdated. I’ve never received a request for a backwards conversion.
