Bug fixes
Broken buttons, failed saves, wrong totals, and VBA errors that stop daily work. I reproduce the failure on a copy, then patch the form, query, or module that caused it.
Microsoft Access Support Services
Keep a live Microsoft Access database working: bug fixes, locking-error fixes, small changes, and maintenance when your team depends on it every day.
What are Microsoft Access support services?
Microsoft Access support services are ongoing help for a database your business already uses. I fix bugs, locking conflicts, slow forms, and small change requests. I also check backups and document how the system works. This is Access database support for day-to-day operations, not a full rewrite.
Excel Access Consultant (EAC) works remotely with copies of your .accdb when possible, for businesses in the United States, Canada, and the United Kingdom. You stay in control of production cutover. Advisory work is billed at $90/hour. Larger change sets get a fixed-price quote before coding starts.
Quick facts
- Best for: live .accdb systems with bugs, locking errors, slow forms, or pending small changes.
- Delivery: remote, working on a copy of your file where possible.
- Rate: $90/hour for advisory and diagnostic work; fixed-price quotes for larger changes.
- Engagement: on-demand, monthly retainer, or project plus support.
- Not covered here: corrupted files (see Access database repair), rebuilds, and SQL Server migrations.
What Microsoft Access support services cover
Support keeps your .accdb usable. It is Access database maintenance services plus troubleshooting when something breaks mid-day.
Slow forms and queries
Forms that lag on open, queries that time out, and reports that freeze the UI. Fixes often include indexes, leaner joins, and removing work that belongs in the back end.
Multi-user and locking problems
Record locks, ghost sessions, and conflicts when several people edit at once. I check split design, linked tables, and how forms lock rows while staff enter data.
Small changes and new reports
Extra fields, new dropdowns, filtered reports, and short VBA tweaks your team needs. Scoped as small support tasks when the change stays inside the current design.
Office and Windows update compatibility
Issues that appear after Microsoft 365 or Windows updates change how Access behaves. I test the same screens your users open after an update cycle.
Backup checks and compact routines
Confirm backups ran, review .accdb growth, and schedule compact and repair off hours. Compact and repair rewrites the file to reclaim space and clear some corruption risk.
Documentation and handover notes
Plain notes on how the front end and back end fit together so the next person is not lost. You keep ownership of every file I touch.
If the file is corrupted or will not open, that is Access database repair, not routine support.
Who this is for
Access support for small business teams that rely on one system and cannot wait for a rebuild project to start.
The developer left
You have a live .accdb and no one on staff who will touch the VBA or linked tables.
You inherited the database
It runs, but tables, queries, and forms were never documented for your team.
It works until it does not
Staff see messages like "Could not update; currently locked" or "Operation must use an updateable query" during busy hours.
More users, more friction
As headcount grows, opens slow down, locks pile up, or someone gets "Unrecognized database format" after a bad copy.
Inherited Access database support usually starts with a short review of the front end (forms, queries, reports, VBA) and the back end (tables on the network share or server). Linked tables are connections from the front end to those tables. A split database keeps those parts separate so more than one person can work at once with less file damage risk.
Multi-user Access means several people open the same data at the same time. Record locking decides whether one person can edit a row while another views it. When locking is wrong, staff see errors during busy periods even though the file looked fine the day before. Ongoing support for a legacy Access database focuses on those operating problems first.
How Access database support works
You get a clear path from the first call to a fixed change, with notes your team can keep.
First response
You describe the symptom, who is affected, and whether the file opens. I tell you if this is support, repair, or a larger project.
Review of the database
I work on a copy when possible. I check the split (front end vs back end), linked tables, recent errors, and how users connect.
Fixes
I repair the failing form, query, or VBA path. I test the same steps your staff take before you put anything back in production.
Documentation
You get short notes on what changed and how to avoid the same break next time.
Ongoing changes
After the fire is out, we can queue small enhancements on demand, under a retainer, or as a scoped follow-on project.
Engagement options
- On-demand: fixes billed at $90/hour for diagnosis and short tasks.
- Monthly retainer: a set block of hours each month, quoted after a short review of your database. Ask for a retainer quote.
- Project plus support: fixed-price build work, followed by a 30-day post-delivery support window, with advisory help after that.
An Access developer on retainer is useful when change requests arrive every week. Pure firefighting can stay on-demand. An Access database retainer is not a blank check. I agree with you what hours cover, what rolls over, and what becomes a separate fixed-price project.
For a practical checklist you can run between support calls, use the Access database maintenance checklist. It covers backups, compact and repair, front-end versions, and lock files.
Support, repair, consulting or migration: which one do you need?
Pick the service that matches the problem. Mixing them on one page would hide the real next step.
| Service | Best for | What you get | Page |
|---|---|---|---|
| Support | A working database that needs fixes and small changes over time | On-demand or retainer help for bugs, locking, reports, and maintenance | Access database support |
| Repair | Corruption, crashes, or a file that will not open | Recovery work, data salvage, and hardening against repeat failure | Access database repair |
| Consulting | Design, rebuild, or major feature work on Access | Fixed-price development for forms, queries, multi-user design, and VBA | Access database consulting |
| Migration | User or size limits that Access alone cannot hold | Move data to SQL Server or Azure SQL, often keeping the Access front end | Database migration |
Larger redesigns belong under Access consulting. Moving tables to a SQL Server back end belongs under database migration.
When support is not enough
Support will not fix a platform limit. If concurrent users keep rising, the back-end file nears practical size limits, or remote staff need a browser instead of desktop Access, it is time to plan migration or modernization. Read when to migrate from Access and whether Access can handle 50 users.
Other signals: weekly corruption after network drops, report runtimes that block the warehouse or finance close, or IT requiring server-side backups you cannot get from a shared .accdb alone. For a SQL Server or Azure SQL back end while keeping Access forms, start with Access database migration. For a browser rebuild path, see Access to web app migration. Until those limits show up, Access database troubleshooting and light maintenance are usually the cheaper path.
Related work
These published case studies show Access systems that need stability, multi-user design, and ongoing care after go-live.
8+ months · zero crashes
15-user manufacturing inventory Access system
After a split redesign and locking fixes, the database ran without a crash for over 8 months. Fifteen users worked at once. The team saved about 10 hours per week previously lost to re-entry and troubleshooting.
Pick time −40%
Warehouse pick lists moved into multi-user Access
A regional distributor replaced printed Excel pick lists with Access pick forms. Average pick time dropped 40%. Re-picks fell from 8% of lines to under 2%.
Quote time → seconds
Retail pricing rules in Access
Pricing rules lived in Access with an Excel front end. Quotes that took 15–30 minutes now finish in seconds, with rules updated in one place for every location.
Access database support FAQ
Direct answers for owners who need ongoing support for a legacy Access database.
What does Access database support include?
It covers bug fixes, slow forms and queries, multi-user locking issues, small feature changes, new reports, update compatibility checks, backup reviews, and short documentation. Corruption recovery is a separate repair engagement when the file itself is damaged.
How much does Access database support cost?
Cost depends on urgency, how complex the VBA and linked tables are, and whether you need one fix or ongoing help. Advisory and diagnostic work is $90/hour. Larger scoped changes get a fixed-price quote before coding starts. See the pricing page for how quotes are structured.
Can you support a database someone else built?
Yes. Most support work starts on systems I did not write. I review the front end and back end, map linked tables, and fix what is breaking before suggesting bigger redesigns.
Does an Access database that already works need support?
Often yes. Backups, compact and repair, front-end version control, and small change requests keep a live system stable. Waiting until the file corrupts usually costs more than light maintenance.
Does Access still work with current Microsoft 365 and Windows?
Yes. Access remains part of Microsoft 365 and Office suites and continues to receive updates. Support work often includes checking that your .accdb still behaves after those updates.
How many users can Access handle?
With a proper split design, many teams run in the teens to low dozens of concurrent users. Past that range, performance and locking risk rise. I cover practical limits in the blog post on Access with 50 users.
How fast can support start?
I schedule support when I am available after a short intake. {{CONFIRM: typical first-response window for non-emergency Access support}}. Urgent corruption is handled as repair, not routine support.
What if the database is corrupted?
That is repair work. I assess whether compact and repair, recovery, or a rebuild is needed, then quote before recovery starts. Use Access database repair for files that will not open or keep crashing.
Related Services & Resources
Need an Access database retainer or on-demand help?
I have 20+ years working on Microsoft Access systems that businesses run every day. Book a free consultation with Robert Terry. Bring the error message and a copy of the file when you can.