From Access application to web application

Many Access applications started as a quick solution and grew into a system the business depends on. Turning such an application into a web application removes most of its limitations, but it is a real project. This page explains what changes, what stays the same and how to approach it without stopping the daily work.

What stays the same

A modernisation is not a fresh start. The most valuable parts of your Access application are carried over:

That is why the analysis of the existing application comes first. Queries, forms and VBA code contain the rules that must not get lost, even if nobody wrote them down.

  • Your data, including the history built up over the years
  • Your business rules: calculations, checks, statuses and the order in which things happen
  • The way your people work: the steps in a process, the lists they use and the reports they rely on
  • Exports to Excel and documents that other people or systems expect

What changes

The technology underneath changes completely. The data moves from an .mdb or .accdb file to a real database such as SQL Server or PostgreSQL, often hosted in the cloud, for example on AWS. The screens run in the browser, on a PC, tablet or phone, without Access installed.

Users log in with a personal account and get permissions that fit their role. Changes are logged, so you can see who changed what. There is no longer a front-end file to copy to every PC, and the 2 GB limit of an Access file disappears.

The look and feel changes too. A web application does not look like your Access forms: it gets its own, contemporary design that works on any screen size. We design the new screens together with your users, so the familiar steps remain recognisable.

Migrating the data

Data migration is often underestimated. Access accepts things a stricter database does not: text in fields that should hold dates, records without a matching parent record, duplicate values or empty required fields. Lookup fields, attachments and OLE objects also need a decision on how to store them.

We therefore build the migration as a repeatable process. It is run and checked several times on a copy of the data before the actual switch, comparing counts and totals, so the final migration holds no surprises.

A phased approach

A big-bang replacement is rarely necessary. A common sequence looks like this:

This keeps the risk small and the daily work running throughout the project.

  • Analyse the existing application and agree on what is still used
  • Move the data to the new database, with the Access screens temporarily linked to it if needed
  • Build the web application part by part, starting where the benefit is greatest
  • Switch over per part once users have tested it, and retire the Access file at the end

Frequently asked questions

Can Access itself not run in the browser?

No. Access is a Windows desktop program. Microsoft's former Access web apps in SharePoint have been retired, so a real web application is the way to make an Access solution available in a browser.

Will the new application look like my Access screens?

No, and that is deliberate. It works in a browser and on any device, so it gets its own contemporary design. The steps and information your users know remain recognisable.

Can we keep using Access during the project?

Yes. With a phased approach the existing application keeps working until each part of the new one has been tested and taken into use.

Where does the web application run?

On a server or in the cloud, depending on your preferences. We often use AWS, where hosting, security and backups are taken care of.

Start with the free scan to see what your Access application contains: tables, queries, forms, reports and code. The analysis runs in your browser and your file is never uploaded. We are happy to discuss the result with you in English or Dutch.

Start the free scan