Microsoft Office Tutorials and References
In Depth Information
Essential Database Concepts
garbage. A well-designed database is easier to maintain than a badly
designed one because each piece of information is stored only once, in a
clearly named field in a clearly named table, with the proper validation
rules in place. Yes, it sounds like a lot of work, but cleaning up a
database of 10,000 incorrect records is (pardon the understatement) even
more work. See Book II, Chapter 5 for ways to avoid GIGO.
Separate your data from your programs. If you create a database to be
shared with (or distributed to) other people, store all the tables in one
database (the back end) and all the other objects in another database
(the front end) . Then you can link these two databases to make
everything work. Separating the tables from everything else streamlines the
whole rigmarole of updating queries, forms, reports, or other stuff later
without disturbing the data in the tables. See Book VII, Chapter 2 for
details on separating a database into a front end and back end.
Back up early and often. Make a backup of your database every day.
With luck, your office already has a system of regular (probably nightly)
backups that includes your database. If not, make a backup copy of
your database at regular intervals, and certainly back up before making
any major changes. See Book VII, Chapter 1 for information on how to
make backups.
 
Search JabSto ::




Custom Search