01Code memory
Nobody understands the VBA code.
Access database developer no longer available
Your Access database developer is no longer available. We can help.
The person who built or maintained your Microsoft Access application may have retired, left the company, changed careers, or simply become unavailable.
Now your business is relying on an application that may contain years of accumulated data, business rules, forms, reports, queries, VBA code, and processes — but nobody on your team knows exactly how it works.
You do not necessarily need a new system. You need someone who can understand the one you already have. The fact that your Access developer is gone does not mean your business application has to go with them.
Begin a DiscussionWhat happens when your Access developer leaves?
The real issue is continuity: who understands the application your business still depends on?
This is not unusual with business-critical Access applications that have evolved over many years. They often continue to work, but the knowledge needed to maintain them has quietly left the business.
02Data model
Nobody knows how the tables relate to one another.
03Reporting
Nobody knows how reports are generated.
04Dependencies
Nobody knows where every database file, linked table, or dependency is located.
05Change risk
Small problems have become difficult to resolve.
06User confidence
Users are afraid to change anything because there is no current documentation.
07Business rules
The application contains undocumented business rules.
08Continuity
Nobody knows whether backups, deployment, or maintenance are being handled properly.
09Next step
The organization does not know whether Microsoft Access remains the right fit.
You do not have to replace the application
Before replacing the system, understand what you already have.
When the original Access developer is no longer available, the natural reaction may be to start looking for a replacement system. That can become an expensive and disruptive decision.
An existing Access application may contain years of accumulated business knowledge. Its forms, reports, queries, and VBA code may represent processes that are critical to the organization but are not documented anywhere else.
We can evaluate the existing database, determine how the application works, identify its strengths and weaknesses, and establish what needs to be done to support it going forward.
In many cases, the most practical answer is to keep the application and establish knowledgeable support around it. If modernization eventually makes sense, you will be in a better position to make that decision because you understand what the existing system actually does.
How we take over and support an existing Access application
A careful takeover process protects the business before changing the technology.
- 01EvaluateWe examine the database and application before recommending changes.
- 02UnderstandWe identify tables, relationships, queries, forms, reports, VBA, macros, and external dependencies.
- 03DocumentWe document important components and business processes that were previously known only to the original developer.
- 04StabilizeWe address immediate problems and risks so the business can keep working.
- 05SupportWe become a knowledgeable resource for ongoing maintenance, enhancements, and troubleshooting.
- 06PlanIf modernization is appropriate, we establish a roadmap instead of forcing an immediate replacement.
What we look at when taking over an Access database
Technical credibility comes from understanding how the whole application fits together.
Simply opening the tables is not enough. A business-critical Access application may depend on hidden relationships among queries, forms, reports, VBA, external files, and user routines.
Takeover audit
Existing Access application
01
Database structure
- Tables
- Relationships
- Primary keys
- Indexes
- Data types
- Referential integrity
02
Queries
- Select queries
- Action queries
- Pass-through queries
- Stored procedures
- Complex joins
- Queries used by forms and reports
03
Application layer
- Forms
- Reports
- Macros
- Navigation
- Startup procedures
04
VBA and business logic
- Modules
- Event procedures
- References
- External libraries
- Error handling
- Business logic
05
External connections
- SQL Server
- Azure SQL
- Excel
- Outlook
- Other databases
- Web services
- File systems
06
Deployment
- Front-end/back-end architecture
- Network configuration
- User environments
- Access versions
- Office versions
What if nobody knows how the application works?
That is often the biggest challenge when an Access developer is no longer available.
The application may work perfectly, but nobody knows what is happening behind the scenes. A form may depend on a query that depends on another query. A report may contain business logic that exists nowhere else. A VBA procedure may automatically update several tables.
Simply looking at the tables does not necessarily reveal how the application works. We can work through the application systematically to identify its major components, dependencies, and business processes.
The result is a clearer understanding of what the application does, what needs attention, and what should be preserved before anyone begins making major changes.
Access application documentation
Documentation turns institutional knowledge into an organizational asset.
01
SchemaDatabase schema and table relationships.
02
InventoryQuery, form, report, macro, and VBA/module inventories.
03
DependenciesExternal dependencies, data flows, startup procedures, and deployment configuration.
04
DecisionsBusiness process descriptions, known issues, recommended improvements, and modernization opportunities.
40+ years of business database experience
Taking over an Access application is not just “finding another programmer.”
Access For Business helps organizations take over, support, document, repair, and improve existing Microsoft Access applications. We evaluate the existing system, determine how it works, identify risks and problems, and establish a practical plan for keeping the application running.
That may mean simply providing ongoing support. It may involve documenting and improving the existing application. Or, if the application has reached the limits of its current architecture, it may mean developing a path toward SQL Server, Azure SQL, or a more modern application.
Ongoing Microsoft Access support
After the takeover, the application needs a responsible support path.
01
TriageTroubleshooting, bug fixes, and user support.
02
EnhanceEnhancements, new reports, new forms, query changes, and VBA modifications.
03
MaintainPerformance improvements, database maintenance, and backup/recovery guidance.
04
ExtendSQL Server or Azure SQL integration when the data layer needs a stronger path.
Is your Access application too old to support?
Age alone does not determine whether an Access application should be replaced.
A 15-year-old application that works well may need less attention than a three-year-old application that nobody understands.
01
RequirementsDoes the application still meet business requirements?
02
Data trustIs the data reliable, stable, and backed up properly?
03
MaintainabilityIs the application maintainable by someone other than the original developer?
04
DependenceHow many users, reports, deadlines, and workflows depend on it?
05
IntegrationDoes it integrate with current systems?
06
Future needDoes it need web, mobile, security, or multi-location capabilities the current architecture cannot support?
When should an Access application be modernized?
Modernization should be based on business requirements, not simply the age of the application.
01
More usersThe user base has grown substantially.
02
LimitsThe database is approaching architectural limits.
03
LocationsMultiple locations need reliable access.
04
Web accessThe application needs web access.
05
Data layerThe data needs to move to SQL Server or Azure SQL.
06
IntegrationIntegration requirements have increased.
07
SecuritySecurity requirements have changed.
08
MaintainThe application has become difficult to maintain.
09
CapabilityThe business needs capabilities the existing application cannot provide.
FAQ
Access developer no longer available questions.
The practical question is not whether someone can write code. It is whether the existing system can be understood, protected, documented, and supported without disrupting the business.
01What should I do if my Access developer is no longer available?First step
Start by preserving backups, identifying the most important workflows, and reviewing the application before making risky changes. The immediate goal is continuity; the longer-term goal is a supportable system.
02Can someone else take over an existing Access database?Takeover
Yes. A knowledgeable Access consultant can review the database structure, forms, reports, queries, VBA, linked data, deployment, and business workflows before providing support or making changes.
03Can you support an Access database created by another developer?Inherited apps
Yes. Many Microsoft Access support situations involve inherited applications. The work starts by understanding how the application is organized and what the business depends on.
04Can you understand an Access application without the original developer?Discovery
Often, yes. The work is slower and more careful, but the application can usually be examined through tables, relationships, queries, forms, reports, macros, VBA, dependencies, and user workflows.
05How do I document an Access database?Documentation
Useful documentation usually includes schema, relationships, object inventories, VBA/module notes, external dependencies, startup procedures, data flows, known issues, and business process descriptions.
06Can an old Access application still be maintained?Supportability
Age alone does not determine whether an Access application should be replaced. A 15-year-old application that works well may need less attention than a newer application that nobody understands.
07Should I replace an Access application if the developer is gone?Decision
Not automatically. Before replacing the application, it is usually better to understand what the current system does, what business rules it contains, and whether support, documentation, improvement, or modernization is the practical next step.
08Can an Access application be migrated to SQL Server?Migration
Yes, in many cases. The Access forms, reports, and VBA may continue to provide the front end while SQL Server or Azure SQL becomes the data backend, but the right architecture depends on the application and business requirements.
Begin a discussion
Tell us what your inherited Access application needs to keep doing.
Share what the application does, who built or maintained it, what users rely on, what is no longer understood, and what cannot be disrupted.
Begin a Discussion