ClassACT Access Database Backups and Corruptions
If the computer running ClassAct is switched off or crashes while the database is open, the database file can become corrupted. ClassAct may report that the database is corrupted next time it is started and will attempt to repair it.
The detection and repair of corrupted databases is handled automatically by the Microsoft Access database engine installed with ClassAct. The database engine does not always detect corrupted databases, in addition, it may not always be able to repair a corrupted database.
From Version 1.0B of ClassAct onwards, a forced repair of the database can be carried out by holding down the SHIFT key while starting the ClassAct Management System.
Note: It is not good practice to switch off a computer until Windows has shut down. If a corrupted file is detected, you should also run the Windows SCANDISK utility to ensure that disk integrity is maintained.
To overcome the possibility of losing data, regular backups must be kept.
ClassAct provides a number of methods of backing up data:
- Use the Datasafe backup utility to save class data to floppy disk, either manually or by setting the ‘Selective backup on exit’ option from Administration Manager.
- From version 1.0B of ClassAct onwards, a complete copy of the database can automatically be created on exit from ClassAct. This feature allows daily or weekly rotational backups to be kept.
Keep a backup of the original database
When the original installation of ClassAct has been made, and all the required lesson modules and report profiles have been installed, a complete backup copy of the database should be made. Proceed as follows:
- Make sure all lesson modules and report profiles and the correct versions of these are installed on the system.
- Exit and locate the LJMS.MDB database file. For ClassAct NT this will be in the C:\LJMS\DATA directory, for ClassAct Lite this will be in the C:\LJCAI\LJMSDATA directory.
- Copy this file to the backup directory (either LJMS\BACKUP for NT or LJCAI\BACKUP for Lite) and rename it to ORIGINAL.MDB
If an unrecoverable database corruption occurs, at least now it will be possible to put back the original database (by doing the reverse of the above) with all the modules and reports present. Then providing that Datasafe backups have been kept on floppy disk, these can be restored and the system recovered.