Convert ADP to MDB

A legacy application may accept only an Access .mdb file, while its existing interface is an Access project connected to SQL Server. Migration requires creating an Access database and deciding which server data and application logic to import, link, or rebuild; renaming the file does not convert it.

What the ADP format is

An Access project (.adp) is a front end for Microsoft SQL Server or MSDE. It contains client-side objects such as forms, reports, macros, and VBA code; its tables, views, and stored procedures reside on the server. Access 2007 and Access 2010 support ADP files. Access 2013 and later do not.

What the MDB format is

.mdb is the legacy Microsoft Access database format used by Access 2000–2003 and supported by later Access versions for compatibility. An MDB can store local tables and Access objects in one file, so it suits older applications that require a Jet database without a separate server. Its maximum file size is 2 GB, and it does not provide SQL Server’s server-side capabilities.

How to migrate the project

1. Back up the ADP and its SQL Server database. Open the project in Access 2007 or 2010; later versions cannot open ADP files.
2. Create a blank Access database and save it in the Access 2002–2003 (.mdb) format. In Access 2007 or 2010, use the relevant Save As option; its menu location varies by version.
3. To make local tables, use Access’s ODBC import option, connect to SQL Server, and select Import the source data into a new table in the current database. Import only the tables the application needs. To keep SQL Server as the back end, link supported tables instead; the MDB will still require the server and a working ODBC connection.
4. Recreate or copy supported forms, reports, macros, and VBA code into the MDB, then reconnect them to the imported or linked data. Check VBA references, controls, and code that depends on ADP-specific behavior.
5. Rebuild required queries in Access. Inspect SQL Server views and stored procedures in SQL Server Management Studio and rewrite their logic as Access queries or VBA where appropriate; T-SQL is not interchangeable with Access SQL.
6. Test data entry, relationships, calculations, forms, and reports in the target Access version. Review SQL Server-specific data types, permissions, and server-side behavior that may not have an equivalent in MDB.

Access 2007 or 2010 is the practical desktop tool for opening the source and creating the target file; SQL Server Management Studio can help inspect server objects. No dependable online converter can perform this migration from the ADP alone, because the ADP relies on a separate SQL Server database and application logic that must be transferred or rebuilt.

Compatibility limits

Imported tables become local MDB data; linked tables remain dependent on SQL Server. Stored procedures, server-side views, security rules, and SQL Server-specific types do not automatically become native MDB objects. If the application depends on those features, retain SQL Server as the back end and migrate only the parts that can run in Access rather than trying to reproduce the entire system in MDB.