The original developer is long gone
An important app still runs the business but nobody on staff knows how it is put together or dares to open the code.
Documented, and someone owns it
Working with Microsoft Access?
Most Access apps that reach us were built years ago by someone who has since left, and the business still runs on them every day. We learn how the thing actually works, keep it running, and move it somewhere safer when the time comes.
What it is
Microsoft Access is a desktop relational database from Microsoft, first released in 1992, and shipped as part of Microsoft 365 and older Office bundles. The .mdb and newer .accdb files hold the tables, queries, forms, reports and VBA code in a single file.
It is often the back end of a departmental app that outgrew a spreadsheet but never made it to a real database or a web application. Plenty of businesses still depend on one of these, and nobody can remember who originally built it.
The honest version
No technology is all upside. This is where Microsoft Access earns its place and where it tends to cause trouble.
Sound familiar?
The Microsoft Access problems that bring people to us, and what you have once each one is fixed.
An important app still runs the business but nobody on staff knows how it is put together or dares to open the code.
Documented, and someone owns it
Usually a bad network write or a crashed client while someone had the file open. The built-in repair gives up and leaves you locked out.
Recovered to a working copy
A single-file database being pounded over an SMB share. Each user drags more data across the wire than they need.
Back end moved off the share
Years of records, images stored inside the database, and bloat from edits that compact-and-repair cannot fully reclaim.
Trimmed, and a plan past 2 GB
A new Office build changes a reference or VBA setting, forms stop loading, and no one on site can read the error.
References pinned, update tested
The business has moved on from one shared office, but the app only works from a Windows PC on the LAN.
Front end on the web, data safe
A copy of the file somewhere on a user's desktop, or a backup job nobody has tested restoring from.
Backed up nightly, restore tried
Linked tables through an old ODBC driver, timeouts on slow queries, or a server move that nothing was told about.
Connection stable and monitored
What we do
Call us for one broken form, or hand us the whole app.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
For a small group of people and a file well under 2 GB, yes, if it is backed up and someone owns it. It becomes risky when the only person who understood it has left and no one has looked at it since.
Yes. The usual route is to move the tables to SQL Server first, keep the Access forms running against the new back end, and then replace the front end with a web app at a pace that suits the business.
Often, yes. We work on a copy, try the tools Microsoft ships first, then fall back to lower-level recovery if those fail. The important step is to stop using the broken file before anything else overwrites it.
Microsoft retired Access web apps in 2018 without a direct successor. The practical options today are a Power Apps front end over a Dataverse or SQL back end, or a regular web application. We help pick the one that fits what the app actually does.
Access was not designed as a true multi-user database. A shared file over the network has every client reading large chunks of it at once. Moving the tables to SQL Server and keeping Access as the front end usually fixes this without rewriting the app.
Estimates are free. Send over the file or screenshots of the forms and errors, and we come back with a scope and a number before anything is touched.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: