Skip to content

Replace your Access database without losing data or rules.

Your Access database has managed orders, maintenance or inspection reports for years. Now it needs to go online, several people need to work in it at once, or the colleague who built it is retiring. We use AI to read out tables, queries, forms and macros and build a web application from them that does the same and is connected to your ERP.

TodayMaintenance.accdb on the file server

only one person can enter data at a time

AI reads alongTables, forms and macros described

Your team confirms the workflows

NewWeb application for all sites

Legacy data migrated and cross-checked

How do you replace an Access database?

In three parts: data, rules, user interface. The data moves to a server database. The rules from queries, forms and VBA macros are written down, confirmed by your team and reprogrammed. The user interface becomes a web application that runs in the browser, also for several users at once and on the move. AI mainly speeds up the second part: it reads the old code and describes what it does. Access stays in operation until the switchover.

A new development is not always necessary. If it is only about more users and data security, it is sometimes enough to move the data to an SQL server and keep Access as the user interface. We clarify that first.

Access was enough for a long time. Now it is reaching its limits.

Several users

“Record is locked.”

When several people work in the database at once, they block each other. Over VPN or from a mobile phone it does not work at all, or only painfully slowly.

Security

A file anyone can copy.

The database sits as a file on the file server. Anyone who can open it can take it with them. One crash while saving, and the file needs repairing.

Knowledge

It was built by someone who is leaving soon.

The macros were written by a colleague or a former service provider. Nobody knows for sure any more what exactly they calculate.

On top of that: data from Access ends up in Excel, the ERP or the online shop via export. Every transfer is manual work and a source of errors.

A maintenance database. What AI finds in it.

A plant manufacturer has planned its maintenance visits with Access since 2008. AI reads the database and produces an overview that the team checks before the rebuild.

Access databaseMaintenance, since 2008
24 tables, 63 queries, 31 forms, 18 reportsFile server, four users, never at the same time

“The database works out the due dates itself. Nobody knows exactly why some plants come up earlier.”

TablesQueriesFormsReportsVBA
OverviewWhat the database does
Rule

Next maintenance after 12 months, after 6 for plants in the food sector.Query “due dates”, field “sector”

Rule

After three faults in a year, the plant is automatically brought forward.Macro when a fault is saved

Notable

11 of 18 reports have not been opened since 2020.Keep or drop?

Data quality

214 plants without a customer, 37 customers entered twice.Clean up before migration

Review

The service manager confirms rules and reports. Then the rebuild starts.

Every item points to a table, query or macro.

Example with sample data – not a customer reference and no guarantee of results.

From Access to a web application in four steps.

It starts with a free introductory meeting. Your team keeps working with Access until the new application delivers the same results. Only then is the switch made.

01

Analyse the database

AI reads tables, queries, forms, reports and macros and creates an overview. We show which of it is still used.

02

Confirm workflows

Your team checks rules and reports: keep, change or drop. After that, it is clear what the new application will do and what it will cost.

03

Build the web application

With a server database, user permissions and interfaces to ERP or accounting. Operation follows what your team is used to.

04

Migrate data and switch over

We rehearse the data migration on a copy, clean up duplicates and check totals and samples. Then the switch happens on a fixed date.

What AI contributes and what your team decides.

What AI takes on

Read, describe, compare

  • Read VBA code, queries and forms and describe them in plain language.
  • Show which tables, queries and reports are connected and which lead nowhere.
  • Find duplicate and incomplete records before migration.
  • Prepare test cases to compare Access with the new application.

What your team decides

What stays, what goes

  • Whether an old rule is still correct today.
  • Which reports and special cases go into the new application.
  • How duplicates are resolved when records contradict each other.

Our recommendation

Do not rebuild one to one

Replacing the database is a chance to get rid of detours. Whatever was only built that way because of Access limitations, such as double data entry or exports for other systems, we replace with an interface. What has proven itself stays.

Replacing it pays off when …

… several people need to work with it at the same time

Including from other sites, in the field or on a mobile phone.

… the database is essential to your business

And an outage would hold up orders, maintenance or inspections.

… data is moved into other systems by hand today

For example into the ERP, accounting or the online shop.

And if not: if two people work one after the other with a small database and everything runs, there is no reason to replace it. We will tell you that in the introductory meeting too.

Advice and delivery from one source.

Whoever analyses your Access database also builds the web application.

Measurable

Tested against Access

Access and the new application process the same real cases. The switch happens when the results match.

Qualification

Certified in AI automation

Certified AI Automation Manager, combined with more than 20 years of software development.

Experience

Databases and web applications since 2002

We build web applications with server databases and interfaces to the systems you already use.

Frequently asked questions about replacing Access.

Is it not enough to move the data to an SQL server?

Sometimes, yes. If it is only about more simultaneous users and data security and Access may remain the user interface, that is the smaller step. If colleagues need to work in the browser or on the move, or interfaces are to be added, there is hardly any way around a web application. We tell you what is enough for your case.

What happens to our reports and analyses?

The reports you need are available again in the new application, as a view in the browser or as a PDF and Excel export. You decide which ones in step 2. This often shows that some of them are no longer used.

How long does a replacement take?

That depends on the size and condition of the database: how many tables, forms and macros, how many special cases. After the analysis you receive a schedule with a fixed scope. Your team keeps working with Access until the switchover.

Will our data go to external AI services?

Not without an explicit agreement. To analyse tables, queries and code, the AI usually needs no real customer data; an empty copy or test data is enough. We set out in writing beforehand what it may see.

Can we extend the new application ourselves later?

Yes. Code and documentation belong to you and are built with common technology. You can extend it with us, with your IT team or with another service provider.

What does it cost?

That depends on the size and condition of the database. In the free introductory meeting, you describe what it does and who works with it. You then receive a written quote for the analysis. You know what the web application will cost after the analysis, before anything is built. We show development and operation separately.

How much longer will your Access database hold out?

Tell us in 30 minutes what the database does, who works with it and what is not working today. You will find out whether replacing it is worthwhile, whether a smaller step is enough and what the start looks like. Free of charge and without obligation.