What to Do When Your Microsoft Access Database Developer Retires
Many businesses have Microsoft Access databases that have been running successfully for 10, 20 or even 30 years. Over that time, the database may have become central to quoting, ordering, stock control, production, invoicing, job management or other day-to-day operations.
The problem often isn’t the database. It’s that only one person really understands it.
When the original Access developer retires, leaves, becomes unavailable or simply no longer wants to support the system, business owners can understandably become concerned about what happens next.
The good news is that an established Access database does not necessarily need replacing just because its original developer is no longer available. In many cases, an experienced Access specialist can take over the existing system, understand how it works, stabilise it and continue developing it.
Can another developer take over an existing Microsoft Access database?
Yes. This is a significant part of the work I do.
A well-built Access application does not depend on its original developer being available forever. An experienced Access specialist can examine the forms, queries, reports, tables, VBA code, linked data sources and integrations to understand how the system operates.
Even where documentation is limited or non-existent, it is usually possible to reverse-engineer an established system methodically.
The first objective shouldn’t normally be to start changing things. It should be to understand the system, identify any immediate risks and establish a safe baseline from which it can continue to be supported.
What should you do if your Access developer is retiring?
If you still have contact with the developer, use the opportunity to gather as much information as possible before they leave. Don’t worry if this isn’t possible — a specialist can still investigate the system afterwards.
- Locate all database files. Identify the Access front end and back end, including any
.accdb,.mdb,.accdeor.mdefiles. If SQL Server or Azure SQL is involved, identify that too. - Make sure you have the source version. An
.accdeor.mdemay be what users run, but a future developer ideally needs the original editable.accdbor.mdb. - Identify where the data actually lives. Don’t assume everything is inside the Access file. Many established applications link to SQL Server, other Access databases, Excel files, accounting systems or external services.
- Secure passwords and credentials. Gather database, SQL Server, VBA, API, hosting and other relevant credentials and store them securely.
- Take a verified backup. Back up the application and its data before making changes. For a SQL Server-backed application, simply copying the Access front end is not a complete backup.
- Document external dependencies. Look for scheduled processes, email accounts, mapped drives, ODBC connections, APIs, Excel imports/exports and integrations with other business systems.
- Record what currently works — and what doesn’t. A short list of known problems, workarounds and business-critical processes can save considerable investigation time.
- Review the departing developer’s access. Once the handover is complete, review VPN, server, cloud and remote-access permissions as you would for any departing supplier or employee.
Do you need to replace an old Access database?
Not necessarily.
The age of an Access database alone isn’t a good reason to replace it. I regularly encounter long-established systems that continue to perform an important business role.
Sometimes the right approach is simply to take over support and make relatively small improvements. In other cases, it may make sense to upgrade an older version of Access, improve the VBA code, move the data to SQL Server or Azure SQL, or add API, web or mobile functionality around the existing application.
The important thing is to assess the system before deciding. “The original developer has retired” does not automatically mean “the database needs replacing.”
What will a new Access developer need to take over the system?
Don’t delay looking for support because you think you need to prepare a perfect technical handover.
Initially, I would normally want to understand:
- What the database is used for
- How important it is to day-to-day operations
- Approximately how many people use it
- Where the Access files and data are held
- Whether SQL Server, Azure or other systems are involved
- What problems or concerns prompted you to seek help
- Whether the original source database is available
From there, the application itself can usually tell an experienced Access developer a great deal about how it has been constructed.
What if there is little or no documentation?
This is extremely common with long-established Access systems and doesn’t necessarily prevent another developer from taking over.
Gather whatever you have: user guides, old specifications, notes, database diagrams, scheduled-task information and details of imports, exports or integrations.
An experienced Access developer can then investigate the application itself — its tables, relationships, queries, forms, reports, VBA code and external connections — to build up an understanding of how it works.
Good documentation makes the process easier, but lack of documentation does not necessarily mean the system has to be rebuilt.
Has Your Access Developer Retired or Become Unavailable?
Taking over existing Microsoft Access systems is a particular area of my work.
I’ve worked with Microsoft Access since 1995 and established The Access Man in 2003. I regularly help businesses where an important Access application has outlasted its original developer, has little documentation, or has become difficult to support internally.
My first priority is to understand what you have and keep the existing system stable. From there, I can troubleshoot problems, provide ongoing development and support, or recommend sensible modernisation where there is a genuine business case for it.
You deal directly with me, Julian Baker, throughout — the same person who investigates, understands and works on your system.
If your Access developer is retiring, has already left, or you’re simply concerned about who will support your database in the future, get in touch for an initial discussion.
