MS Access Data Project Application (ADP)

This approach “Internet enables” the MS Access application, but does cause performance issues and is expensive to maintain. An MS Access Data Project (ADP) replaces the native MS Access Jet Engine datastore with a SQL Server database. This configuration requires that all queries in the MS Access application be replaced with SQL Views, Functions and Stored Procedures (the most appropriate SQL technique). Users access the individual MS Access forms via a standard web browser.

MS Access Data Project (ADP) Application Scorecard

MS Access Data Project Application (ADP) Limitations

Developing MS Access Data Projects does make the MS Access application “a web based database available on the Internet,” but also requires that Users run the MS ADP application through the MS Internet Explorer browser, and each User must have a locally installed copy of MS Access (or the appropriate MS Access Runtime engine) for the web-based database application to function properly.

MS ADP applications are limited primarily due to more complex deployment issues such as MS Access Runtime and/or IE Browser availability and version issues. While overcoming some of the inherent MS Access multi-user deployment limitations, the MS Access Data Project approach can also suffer from poor performance, unlike in standard web based database applications, due primarily to the start up of the local instance of MS Access. Data security, reliability and integrity are Excellent, albeit entirely dependent on the SQL Server design.