Split MS Access Application

The Split MS Access approach is a superior method for deploying MS Access applications within a LAN environment. This approach requires “splitting” the MS Access application into 2 MDB files: one that contains the Front-End Application components (User Interface Forms, Queries, code, etc.) and another MDB file that contains the Back-end datastore component.

Splitting an MS Access application into front-end and back-end components can incrementally improve application reliability, but will come at the cost of performance. Splitting an MS Access application is a good idea to support small LAN workgroup environments.

Split MS Access Application Scorecard

Sharing Data With A Split MS Access Application

It is fairly common to use the Split Access method to support different MS Access Front-End applications that are connected to a single back-end MS Access datastore. For example, a single MS Access datastore that contains Customer Contact data connected to different MS Access applications in the Marketing and Customer Support departments.

The benefits of splitting an MS Access application are limited: you cannot share the application across a Wide Area Network (WAN) or scale application use beyond a dozen or so simultaneous users.