Back up a database Access 2007
Author: mety Labels:: Back up a database Access 2007Backups help protect a database from system failures and help protect against mistakes that the Undo command cannot fix. In Microsoft Office Access 2007, you can use the Undo command up to 20 times to reverse changes that you made since the last time that you saved your database file. However, when you use an action query (action query: A query that copies or changes data. Action queries include append, delete, make-table, and update queries. They are identified by an exclamation point (!) next to their names in the Database window.) to delete records or to change data, you cannot undo those changes by using the Undo command. For example, if you run an update query, any old values that were updated by the query cannot be restored by using Undo. Tip Consider making a backup immediately before you run any action query, especially if the query will change or delete a lot of data. Not all changes in a database can be undoneAlthough Access offers you the option to reverse changes that you decide you did not want to make, the process is not foolproof. To prepare for recovery from unwanted changes that you cannot undo, you should make backups of your database. Regular backups are essentialTo decide how often to make backups, consider how often your database changes:
Back up a databaseWhen you back up a database, Access saves and closes any objects that are open in Design view, compacts and repairs the database, and then saves a copy of the database file by using a name and location that you can specify. Access then reopens any objects that it closed. Note Access will reopen objects as specified by the value of the objects' Default View property.
Back up a split databaseA split database typically consists of two database files: a back-end database, which contains only data in tables, and a front-end database, which contains links to the tables in the back-end database, in addition to queries, forms, reports, and other database objects. All the data is stored in the back-end database. All the user interface objects, such as queries, forms, and reports, are kept in the front-end database. When you back up a split database, you back up the front-end and back-end databases independently of each other. It is more important to make regular backups of the back-end database, because it contains your data. You can make a backup of the front-end database whenever you change its design. However, because each user has an individual copy of the front-end database and can make arbitrary design changes, you should also consider requiring those users to make their own backups of the front-end database. Back up the back-end databaseBecause running the backup requires exclusive access to the database file, users may be momentarily unable to use the back-end database. You should consider notifying users before you start the backup process.
Back up the front-end databaseTo protect your investment in the design of your front-end database, you should back up the front-end database whenever you change its design. If you allow users to customize the design of their own copies of the front-end database, you should consider requiring them to back up their own customized copies. To back up the front-end database, leave the database open immediately after you change its design. Then follow the steps in the section Back up a database, starting at step 2. After you finish the backup operation for the front-end database, you can then make the new design available to users |