How to Install Your Database Download
Download Files & Installation Requirements
Any Access databases that you download from our website will be contained in a compressed zip folder. You MUST remove the database files from the zip container before operating the database, otherwise, the database will not function correctly.
The database you download could be designed to operate in either a Standalone or Front-End/Back-End configuration (see below), so the zip container might contain a single or multiple files, including a ‘README.txt’ file. If provided, refer to the ‘ReadMe.txt file for detailed installation instructions
Under no circumstances should you install or attempt to operate an Access Database from a replicated folder (a folder on a replicated network server) or from a shared Internet folder such as Drop-Box, particularly if the database will be accessed by multiple users.
Installing The Database
Single User Database
- 1. if you don’t have Microsoft Access Database installed on your computer see our FAQ ‘Do I need Access Database Installed’
- 2. Identify or create a folder on your PC or network in which the database will be permanent located. The folder MUST not be a replicated folder (such as a drop box folder).
- 3. Add the folder to your existing backup regime (if not already included)
- 4. Extract all files contained in the downloaded zip file to the selected/created folder.
- 5. In the folder, locate main database file ( Database Name.xxxx ) and double click to start the database.
- 6. If required create a shortcut from the database file and place it on your desktop. You can then start the database by clicking the desktop shortcut.
Multiple User Access Database
There are two options for installing an Access Database that will be used over a network by multiple users. The method you use depends on the format of the database you downloaded. A standalone formatted database will have a single database file whereas a Front-end/Back-end configured database will contain two database files (i.e Assets.accde and AssetsBE.accdb).
Method one requires a little more set up, but it also provides significantly better database performance and virtually eliminates any likelihood of user conflicts occurring. It is the superior installation method and the recommended option.
- 01. Applies only for databases that were supplied in 'Front-end/Back-end’ configuration.
- 02. Identify or create a folder on your PC or network in which the database will be permanent located. The folder MUST not be a replicated folder (such as a drop box folder).
- 03. Add the folder to your existing backup regime (if not already included)
- 04. Extract ONLY the database tables (Back-End) file (Database_ NameBE.accdb’) and save it in the selected folder.
- 05. On EACH USER’S local computer create a local database folder (i.e. “C:\My Database\”)
- 06. Extract the Database Front-End file (‘Database.accde’) along with any other sundry files into this local folder.
- 07. Manually create a shortcut to the database file and copy it to the desktop.
- 08. Double click the shortcut to start the database.
- 09. If prompted with a security warning when starting the database, click the option that allows the database code to operate.
- 10. When prompted, use the provided file browser and locate the tables (back-end) file on the network share, Double click or select the file name and the database will automatically link the to the tables.
- 01. Create a folder on your PC or network which will be the permanent location for the database. The folder MUST not be a replicated folder (i.e. drop box).
- 02. Add the folder to your existing backup regime (if not already included).
- 03. Extract all files in the downloaded zip file into to the folder that you created.
- 04. Click on the file Database_Name.accde and select ‘Create Shortcut’. Make a copy of the shortcut and paste on your desktop.
- 05. Double click the shortcut to start the database. If prompted select the option to allow the database code to operate.
- 06. Back-end tables should auto-link, but if not use the provided file browser to locate the tables database, and double click the file (Database Name with '_BE' appended)
- 07. Ask each user to copy the database shortcut that you created at step 04 to their desktop.
- 08. See Microsoft Access Database Configuration Options (below) for more information
Microsoft Access Database Configurations Options
In a standalone configuration, an Access Database consist of a single database file containing both the users interface objects (forms, reports and functions) as well as the database tables in which the data is stored.
Multiple users can share a single file Access database over a network, however, it could result in data conflicts and other similar issues occurring. Unlike an Access database in a back-end/front-end configuration, a single file database delivers both the data and the user-interface objects across the network which can impact database speed and performance. In an environment with less than 5 to 10 simultaneous user, this is generally not an issue, but as the number of user's increase, the performance degradation does become more noticeable.
Front-End / Back-End Configuration (Split Database)
A front-end/back-end configuration is the recommended method for deploying an MS Access Database that will be shared by multiple users across a network. In this format, the Access database is split into two separate access database files that are linked and operating as a single unit.
The front-end database includes only the users interface objects such as the Queries, Forms, Reports, Macros, and Functions with which the users interact with the stored information, but none of the stored information itself.
The Back-End contains only the database tables in which the data (information) is actually stored but contains none of database objects the user interacts with.
Significant performance gains are achieved when the database tables (back-end) are stored in a shared folder on the network and the database User Interface (front-End) is installed in a folder on the user’s local computer. This configuration avoids the necessity to move user-interface objects, such as forms, queries, and reports, across the network thus reducing the amount of network traffic the database creates. This configuration also virtually eliminates any opportunity for user data access conflicts to occur.