When creating Access applications to be used on a network by multiple people it is recommended that it be split up using a frontend, which contains queries, forms, reports, macros and modules, and a backend, containing only tables. The front end would then contain links to the backend, and the backend database is stored on a shared location, and front ends distributed to the users machines.

While there are a number of advantages to designing the application this way, such as not having to worry about corrupting the users data as working on the forms and reports, or even pulling in specific objects. The main problem is distributing a new version of the front end database. This application helps manage that by using a table in the front end to manage the version number.