What an ADP is and why it stopped working
In an ADP the tables, views and stored procedures are not in the Access file but in SQL Server. The .adp file contains only the forms, reports, macros and VBA modules, connected to the server through OLE DB. A compiled version has the extension .ade.
Microsoft removed ADP support in Access 2013. Later versions, including Access in Microsoft 365, cannot open or convert .adp and .ade files. Organisations that still use one depend on an older Office installation, which becomes harder to keep running with every Windows and security update.
The strength: your back end is already SQL Server
Unlike a classic .mdb application, the data and often much of the logic are already on a proper database server. Tables, relationships, views, stored procedures and triggers can usually stay as they are, possibly after a move to a supported SQL Server version or to the cloud.
The work is therefore mainly in the front end: the forms, reports and VBA code that users work with every day.
Your options
Which option fits depends on the number of forms and reports, the amount of VBA code and how much of the logic already lives in SQL Server.
- Convert to an .accdb with linked tables. The forms and reports are imported or rebuilt in an .accdb file that connects to the same SQL Server through ODBC. Record sources based on views or stored procedures often need pass-through queries or other adjustments, and code written for ADO and the ADP object model has to be reviewed.
- Build a web application on the existing database. The SQL Server database stays; a new browser-based front end replaces the ADP. This removes the dependency on Access altogether and gives users access from any device.
- Combine both. First a short-term .accdb solution to get off the unsupported version, then a gradual move to a web application.
What to inventory first
For a sound choice you need to know both halves of the application: the ADP front end and the SQL Server database. AccessDB Rescue reads .adp files and can also analyse a SQL Server backup (.bak) or an exported structure (.sql/.csv). It shows the forms, reports, macros and VBA code next to the tables, views and stored procedures, and links the two together.
Of an .ade file the structure can be read, but not the VBA source code. For that you need the original .adp.
Frequently asked questions
Can Access in Microsoft 365 open an .adp file?
No. Since Access 2013, Access no longer supports Access Data Projects. Neither .adp nor .ade files can be opened or converted in current versions.
Does our SQL Server database have to change?
Not necessarily. In most cases the database can stay. It may be a good moment to move to a supported SQL Server version or to the cloud, but that is a separate choice.
Can the forms be converted automatically?
Partly. Forms and reports can be brought into an .accdb, but record sources, ADO code and server-specific features usually need manual work. How much depends on your application.
Do I have to send you our SQL Server backup?
No. The scan reads the backup or structure file in your browser. Only a summary with counts reaches our server, never your data or the file itself.
Scan your .adp file and, if you have it, a SQL Server backup or structure export to see both halves of your application. Everything is analysed in your browser and nothing is uploaded. Then talk to us, in English or Dutch, about the best route.
Start the free scan