(877) 519-4537 info@arkware.com

When you split a database, it means that you reorganize it into two files. One file is the back-end database that contains the data and tables. The other file is the front-end database that contains the queries, forms and reports. Users interact with the data by using a local copy of the front-end database. 

In Microsoft Access, you can split a database using the Database Splitter Wizard. This is one of the many reasons why we love Access – it makes completing tasks like these quick and easy! Once you split the database, you’ll have to distribute the front-end database to your users. 

Let’s learn more about why you might want to split your database and the benefits to doing so. 

Why Should I Consider Splitting My Database? 

Not all databases need to be split, but it’s something to consider from an architectural point of view. By splitting your database into a front- and back-end, you can improve database performance, reduce the risk of corruption and even save money. 

When you split an Access database, you create two files. The back-end database contains just the tables, while the front-end has everything else: queries, forms, macros, reports and modules. All of this can be distributed to users without giving them access to your tables. 

And, with the Database Splitter Wizard, splitting a database is generally very simple. However, if you plan to split a large or more complex database, we recommend speaking with a database expert like Arkware first. 

What are the Benefits of Splitting an Access Database? 

There are a number of advantages to splitting your database:

  • Improved performance. Split databases have significantly improved performance because only the data is sent across the network. In a database that’s not split, all of the database objects have to be sent across the network as well, not just the data.
  • Greater security. Since users don’t have direct access to the tables, there’s less risk of them accidentally deleting tables or stealing data. You can also restrict front-end users from making changes to the application. 
  • Better reliability. Splitting your Access database reduces the risk of database corruption. If there is an issue for an individual user, it’s usually related to that user and not the database as a whole. 
  • Enhanced flexibility. Because each user works with a local copy of the front-end database, users can create queries, forms and other database objects without affecting other users. 

Contact Arkware to Split Your Database 

Think database splitting is right for your database? Contact Arkware for a consultation. If you have a small and streamlined database, you can likely split your database on your own using the Database Splitter Wizard. More complex databases can benefit from our help!