Microsoft Office Tutorials and References
In Depth Information
Splitting Your Database into a Front End and a Back End
important, consider storing it on a network server or at least on a little-used
or lightly used PC.
For more information on sharing files on a LAN, read Windows 8 For
Dummies, Windows 7 For Dummies, Windows Vista For Dummies, or Windows
XP For Dummies, all by Andy Rathbone (John Wiley & Sons, Inc).
Splitting Your Database into a
Front End and a Back End
If you create a multiuser database, consider splitting your database into two
pieces: the data (the tables and the relationships among them) and
everything else. The database with the data is the back end, and the database with
everything else — the queries, forms, reports, macros, and Visual Basic for
Applications (VBA) procedures — is the front end. You and other database
users open the front-end database, which contains links to the tables in the
back-end database.
Why split?
Splitting your database has some advantages. Here are two scenarios that
have nothing to do with multiuser databases:
Book VII
Chapter 2
You don’t need to back up the front end nearly as often as the back
end because the front end rarely changes. By splitting your database
into two files, you can back up just the back end, where the constantly
updated data lives. (You do back up your data every day, right? See
Chapter 1 of this minibook to find out how.)
You improve the front-end database and replace everyone’s old
frontend database with your new one without messing up each person’s
data, which is stored safely in the back end. You may create a database
that tracks church members, committees, and donations, for example,
and then sell the database to zillions of congregations. By splitting the
database, you can provide updates to the front end later (with improved
forms, reports, and programming) without disturbing each
congregation’s data in the back-end database.
Splitting your database is even more important if you create a multiuser
database in which everyone opens the same forms and edits the same data,
possibly at the same time. Here’s why:
Each person has his or her own front-end database with user-specific
forms and reports. All the front ends can connect to the shared
backend database. Each user is free to make new queries, forms, and reports
in the front-end database without affecting any other user.
Search JabSto ::




Custom Search