Microsoft Access guidance
Hiring a Microsoft Access Developer: A Buyer’s Guide
Choose an Access developer who can explain how they will understand the business process, protect the existing application, and leave it supportable. Coding ability matters, but so do continuity, testing, and a clear handover.
Prepare a brief before requesting an estimate
Describe what the application does, who uses it, and the change or failure that prompted the inquiry. Include the reports and deadlines that cannot be disrupted. You do not need to know the technical cause to explain the business impact.
Identify whether the original developer is available and whether editable source files, deployment notes, and backups exist. Discuss a secure transfer method before sharing database files; do not place business records or credentials in an initial inquiry.
- What must keep working during the engagement?
- Which Access files and external systems are involved?
- Who can confirm whether a proposed change works correctly?
- What documentation and source material are available?
Ask how the developer investigates an inherited system
Ask for an explanation of how forms, reports, queries, VBA, and linked data will be traced. A competent investigation should connect the reported symptom to its dependencies rather than edit the first object showing an error.
Discuss how work will be isolated from production. Agree on backups, test copies, access permissions, and the point at which a user will validate the change. Be cautious about a fixed recovery promise made before anyone has examined a damaged file.
Agree on evidence of completion
Define a small set of observable acceptance criteria. For a report change, this could mean matching agreed totals for a known period and handling a specified exception. For a new form, it might mean creating, validating, editing, and retrieving a record without disturbing existing workflows.
Ask how deployment and rollback will work. An update that runs on the developer’s machine is not sufficient evidence that each user has the correct front end, references, permissions, and connected data.
Make ownership and handover explicit
Agree in writing on access to editable source, the scope of documentation, responsibility for credentials, and the support arrangement after delivery. Confirm these terms rather than assuming they are included in every proposal.
Useful handover material can include a dependency inventory, release notes, deployment steps, known limitations, and an explanation of important business rules. Ask which of these will be included in the agreed scope.
Compare proposals by scope
Compare the investigation, implementation, testing, deployment, and support work included in each proposal. A lower estimate may cover a narrower task. Ask what assumptions could change the estimate and what happens if investigation reveals a different problem.
If replacement or SQL Server migration is proposed, ask why the current application cannot meet the requirement through a smaller change. The recommendation should follow from the business need and the application evidence.
Continue with your application
- What to Do When the Access Developer Is No Longer Available
- Access Development
- People and Project Experience
Describe the application, the change you need, and what must keep working. We can discuss the appropriate next step.
Begin a Discussion