A PRACTICAL SOLUTION / LEGACY ACCESS DATABASE MODERNIZATION
Keep the knowledge. Improve the database.
An Access application can hold years of useful rules, forms, queries and hard-won knowledge. Moving it without understanding those dependencies can create a different version of the same problem.
SOUND FAMILIAR?
When this is worth a closer look.
- Only one person understands how the application works.
- Reports, forms or linked tables are becoming difficult to maintain.
- More people need access than the original design anticipated.
HOW WE APPROACH THE PROBLEM
Understand the dependencies.
Choose what to improve.
- 01
Understand the application
Inventory tables, relationships, queries, forms, reports, VBA and external links. Walk through the actual work with its users.
- 02
Choose what to preserve
Compare repairs and documentation, a different database back end, or a new interface. The right choice depends on the application and its users.
- 03
Migrate deliberately
Agree mappings, test representative records and reports, rehearse cutover, and retain a rollback option before any live change.
ILLUSTRATIVE EXAMPLE
How this could work.
A manufacturer has an Access tool that still does its job, but its reporting is difficult to maintain. An assessment could recommend documenting the application and improving its data layer before considering a replacement.
POSSIBLE PROJECT DELIVERABLES
Something you can use
and take ownership of.
- An agreed inventory of dependencies and business rules
- A recommended improvement or migration scope
- Validation criteria, cutover responsibilities and handover documentation
YOU DON’T NEED EVERY ANSWER YET
Useful questions to begin with.
- Which version of Access and which linked data sources are involved?
- Who uses the application, and where does it interrupt their work?
- Which reports and calculations must reconcile after a change?
Describe the situation in general terms. We can agree a suitable way to review sensitive records or technical details later.
Let’s look at the problem ↗