What is inside your Access application?

Before you can plan a modernisation, you need to know what you are modernising. Many Access applications have grown over the years, built by several people and with little documentation. This page explains what an inventory should cover and how to get one quickly.

Why an inventory comes first

An estimate without an inventory is a guess. Two Access files of the same size can differ enormously: one contains mostly data, the other hundreds of queries and thousands of lines of VBA code. The effort of a migration lies in the logic, not in the number of megabytes.

An inventory also shows what is no longer used. Objects that have not been changed for years, empty tables and test copies of forms do not need to be rebuilt. That saves time and keeps the new application clean.

What to look at

A useful inventory covers at least these parts of the application:

  • Tables: fields, data types, primary keys, indexes, relationships and the number of records
  • Queries: especially queries that change, add or delete data, nested queries and references to forms
  • Forms and reports: how many there are, what they are based on and which events they use
  • Macros and VBA code: size, procedures, Windows API calls and links to Excel, Word or Outlook
  • Linked tables: other Access back ends, Excel and text files, ODBC connections to SQL Server or other databases
  • Settings and usage: startup form, creation date and the last design change per object

Doing it yourself or using the scan

Access has a built-in Database Documenter that prints the properties of objects. For a large application that easily runs to hundreds of pages, and it gives no overview of complexity or points of attention. It also requires a version of Access that can open the file, which is a problem for Access 97 and ADP files.

AccessDB Rescue reads the file without Access, from Access 97 to Microsoft 365, including .adp files. Within seconds the scan gives totals, an indication of the size of a modernisation and a list of points of attention. If your application consists of a front end and a back end, scan both files together: the scan links them.

What the scan does not see

The scan reads the structure and the code, never the content of your records. It cannot see what your screens look like or how your users actually work, and of compiled files (.mde/.accde/.ade) it cannot read the VBA source code. Data in other files that the application links to is not included either.

Those are exactly the topics of the follow-up conversation: together with the people who use the application, we complete the picture and translate it into a realistic plan.

Frequently asked questions

Which files can I scan?

.mdb, .mde, .accdb and .accde files from Access 97 to Microsoft 365, Access Data Projects (.adp/.ade) and, optionally, a SQL Server backup (.bak) or structure export (.sql/.csv).

My application consists of two files. Which one do I scan?

Both. Add the front end with the forms and code and the back end with the tables together; the scan links them and shows the complete application.

My database is protected with a password.

Older .mdb passwords are usually no obstacle. For encrypted .accdb files the scan asks for the password. It stays in your browser and is never sent.

What do you receive from my scan?

Only a summary with counts, such as the number of tables, queries and lines of code. Never your data, object names or the file itself.

Start the free scan and get an overview of your Access application in seconds. Your file is analysed in your browser and never uploaded. Want to discuss the result? We talk in English or Dutch, without obligation.

Start the free scan