Split Database) I have done both of the above. The other file is the front-end database that contains the queries, forms and reports. The front end is quite loaded with queries, reports, forms, macros etc and the back end simply has the tables. 30 - 40 seconds go by after you click an item until it lets you edit it or change it. As to the comfidentiality issue, to "copy" the back end. To remove reliance on local hardware our Group IT want to run all apps in the cloud. Check out the database file name and type and do if any necessary changes you need to do it. Next, click Split. Click on Options. Encrypting a database makes the data unreadable by other tools, and it sets a password that is required to use the database. My question is, where is the front end. One file is the back end database which contains all the tables and data. unsplit database | Access World Forums Notes: Consider using the name that Access suggests. Splitting Access database involves separating the database into two files. Click the Access Database button. Let the Access wizard split the database (without the linked tables). A dialog box appears, informing you that the database has been successfully split. Users interact with the data by using a local copy of the front-end database. I split my database, compacted and repair, did as much as I could the performance analyzer suggested without compromising functionality and controls, converted the front end into an MDE file and put the BE on a network path (and of course all the tables are linked), with the FE hosted locally by the testing workstation. For years I have been running a split access database across a local LAN, the mechanics of which I understand. For more information, see our paper on Microsoft Access Split Database Architecture to Support Multiuser Environments, Improve Performance, and Simplify Maintainability. First, you must encrypt the backend/source database. Pros and Cons about splitting a database "Split" Databases. This database will be used for a one time data transport to another system, containing order of a few million entries. Split the database into two files . After some research into who all was actually opening the file (I had a list of people who were SUPPOSED to be accessing it, but that differed from what the user was saying and what the reality of the situation was) I found that people kept opening the actual database backend instead of any sort of front end and only had read-only permissions .