Microsoft Office Tutorials and References
In Depth Information
Splitting Your Database into a Front End and a Back End
If you have queries, forms, reports, or macros that you want to make
available for use after the split, be sure to export them to files so that
they can be imported back into all the new front ends that people will be
using.
You can protect the front-end database by saving it as an .accde file.
(See Chapter 3 of this minibook for instructions.) People can’t change
the VBA code, macros, forms, or reports in an .accde file.
Performance is better. Your database will run faster if the front-end
objects — queries, forms, and reports — are stored on the local computer
instead of transmitted across the LAN.
Security is better. In an organizational setting, if you store the back-end
database on a file server, it can be backed up with the rest of the files on
the server. Also, security on a server usually is better than security on a
local PC.
You can move back-end data without changing the front end. If the
database grows into a huge project, you can move the data from the
back-end Access database to a larger database system (such as MySQL
or SQL Server) without changing the Access front end. Your Access front
end can link to large corporate databases as well as to an Access
backend database.
A few disadvantages exist, of course:
You need to keep track of both files. You can’t get far with only one of
the two databases. If you need to move your database to another
computer, be sure to move both files. Back up both files regularly, too.
If you want to change the design of the tables in your database,
remember to make your changes in the back-end database. Make sure
that the links still work from the front end.
Let’s split!
Access comes with a Database Splitter Wizard that splits a database into
front and back ends and also creates the links between the two databases.
To split your database into front-end and back-end databases, follow these
steps:
1. Make a backup copy of your database.
You never know what could go wrong, and you certainly don’t want your
entire database to get trashed. (See Chapter 1 of this minibook for info
on backing up your database.)
2. Open the database.
Close all tables and anything that may refer to a table, because the
wizard can’t run if any objects are open.
Search JabSto ::




Custom Search