Microsoft Access 2021 Advanced: Splitting a Database

Name: Microsoft Access 2021 Advanced: Splitting a Database
Author: John Varan

Learn about why you should split databases and how to do so

Preview the first lesson free — get full access to all 3 lessons.

Course: On-Demand

Hello, my name is John Varon, and in these lessons, you will learn about splitting a database. In this lesson, I will show you why you may need to split a database. Splitting a database refers to taking an existing database and separating the objects in it into two or more different databases. These different databases are then linked back together so that functionally they act like a single database again. While it is possible to split a database into more than two parts, by far the most common approach is to use only two parts. The complication resulting from using more than two parts usually tends to not make up for the benefits, but sometimes it does. As to why you would want to split a database, there are several scenarios where it can be useful. One reason could be to save on storage space. If your database is getting bigger and bigger over time, it can have a significant impact on performance, especially with Microsoft Access. This is because Microsoft Access doesn't have a client -server architecture, and instead is meant to be opened as a single file. This means it has no functionality for handling large data transfers across network connections. In this case, you could split the database and put the larger tables into a different database, possibly even one that's not Microsoft Access and which has a client -server architecture. The remaining Microsoft Access database would use table links to connect to this server database. Another potential reason to split a database is for separation of concerns. Separation of concerns means splitting database objects based on who will be responsible for them and using them. Users who perform different roles would use different databases. Usually, this separation is based on the difference between administrative users versus end users. Security can be another reason to split a database. This split would be done very similarly to the previous one, the separation of concerns. In fact, it could be argued that it is just a different version of separation of concerns. This time, it's just between users that have access to secured information and users that do not. In this scenario, tables that contain sensitive or secured data would be stored in the back -end database, while the other tables would be stored in the front -end database. Users of the front -end database would have only read -only access to the link tables in the back -end database, and only users with secure access would have access to the editable tables in the back -end database. While these are the most common reasons why one might want to split a database, there could potentially be others depending on your specific needs. It can be a very useful tool for solving problems that can't be easily solved by other means. Thanks for watching. Stay tuned for the next lesson, where I will show you how to create a front -end database.

Advanced Provider : John Varan 3 Lessons · 18m in Arabic, German, English, Spanish, French, Portuguese, Chinese

Course Description

Splitting a database is a common technique that is used for solving various issues that can arise with database applications, which is why this course will explain what these different issues or problems are and discuss how splitting the database can resolve each situation. Knowing how to create front-end and back-end databases is an important skill for anyone using Microsoft Access, and this course will show you how to do this by offering a step-by-step example of how to create each, starting from the initial backup of a single database. This course will also build on your understanding of Microsoft Access 2021 databases by showing you how to connect and link the two halves of a split database together to make a functioning database application that behaves as a single database.

In this course, you will learn about the different reasons why you should split a database in Microsoft Access 2021. We will explain how to create a split database with step-by-step examples for both front-end databases and back-end databases. We will also discuss how to connect the two split portions of the database to function as a single database again.

What You'll Learn

Understand why you should split a Microsoft Access 2021 database and how to do so
Create a front-end database following a step-by-step example
Create a back-end database starting from a backup of a single database
Connect and link the front-end and back-end halves so they function as a single database
Identify the different issues and problems that splitting a database can resolve

Key Takeaways

Splitting a database is a common technique used to solve various issues that can arise with database applications.
The course explains the different reasons why you should split a database in Microsoft Access 2021.
It demonstrates how to create both front-end and back-end databases with step-by-step examples, starting from the initial backup of a single database.
It shows how to connect the two split portions of a database so the application behaves as a single, functioning database.
Knowing how to create front-end and back-end databases is presented as an important skill for anyone using Microsoft Access.

Frequently Asked Questions

Who is this course for?

It is for anyone using Microsoft Access who wants to learn how to split a database, since knowing how to create front-end and back-end databases is described as an important skill for Microsoft Access users.

What does this course cover?

It covers why you should split a database in Microsoft Access 2021, how to create front-end and back-end databases with step-by-step examples, and how to connect the two split portions so they function as a single database again.

What skills will I gain from this course?

The course covers skills including Microsoft Access, Database Application, Database Development, Database Partitioning, Database Programming, and Microsoft Data Access Components.

What lessons are included?

The course includes three lessons: Why Split a Database?, Creating the Front-End Database, and Creating the Back-End Database.

Does this course show how to reconnect the split database?

Yes. It discusses how to add links between front-end and back-end databases and connect the two split portions so the database functions as a single database again.