A Database Utility program is available that has three functions:-

• Database reorganization, to remove the unused space that accumulates in Pedigree Sofware's databases after a lot of data entry and editing.
• Creating a copy of a database as one of a different size-type, for example, name.ped to name.pdg.
• Database repair, when PediTree cannot open a database, or experiences difficulties in Check DB or GEDCOM export.

The Database Utility is available for download here, as an installer (version 2.4.5, 860Kb). Once downloaded, double-click on the file to install the utility program and its help-file. Entries for the program and its on-line help are added to your Start menu under Start > Programs > Pedigree. See the on-line help for further information.

To reorganize a database, proceed as follows:-

1. Close PediTree.
2. Make a back-up copy of the database.
3. Use the Database Utility to check and reorganize the database.
4. Open the database in PediTree.
5. Run File > CheckDB to check that all is well.
6. Close PediTree.
7. Re-run the Database Utility and remove the pre-reorganize version of the database that it retains.

The steps to be taken in repairing a database are documented in the on-line help. They are:-

1. Make a back-up copy of the faulty database.
2. Use the Database Utility to inspect the database and erase any faulty records reported. Then use Reorganize on the error-free database to correct its un-used space records.
3. Open the database in PediTree. Confirm PediTree's request to fix any indexes.
4. In Update mode, run File > CheckDB to report and correct any errors.
5. If you have used the Database Utility Reorganize process, then
   1. You can now add any missing records and delete any blank records corresponding to deleted records in the old database. (These will appear at the beginning of standard indexes.)
   2. Re-run the Database Utility and remove the pre-reorganize version of the database that it retains.
6. If, however, you have not used the reorganize process, then do not add back any missing records at this stage, but proceed as follows:-
   1. Use File > Save As GEDCOM > GEDCOM 4 Pedigree to export the whole database. Say 'Yes' to preserving RINs, so that you can easily identify links in the deleted record(s) to ease replacement later.
   2. Use File > NewDB to create a new empty database, opting to keep the Indexes
   3. Switch to Update mode, then use File > Import > GEDCOM to import the GEDCOM file exported above.
   4. You can now add any missing records and delete any blank records corresponding to deleted records in the old database. (These will appear at the beginning of standard indexes.)
   5. When satisfied with the new database, you can delete the old one.

If you have need to use this tool to repair a database, please let Murray Kennedy and/or Colin Liebenrood know that you have done so. We need to gauge its usefulness and how frequently it is needed.

Version 2.4.5: one warning changed to error (for Pedigree users); layout tolerant of text-size changes in Win 7 and later; fixed a bug when processing more than one database in a single session.

Version 2.4.4 fixed an issue with a massively-corrupt database.

Version 2.4.3 fixes issues with installation and use under Win 7 64-bit.

The following changes were made between versions 2.3.0 and 2.4.2.

• Display of stored data, as a percentage of maximum capacity. This may appear as a single figure, such as 49%, or a dual figure such as 55%/49%. This latter form shows both the current value, with unused space, and the value that would apply if the database was reorganised.
• The ability to process databases that have one or more space-files missing. These missing files can be re-created by using the Reorganise process.
• Additional hints of the actions that need to be taken to repair a faulty database.
• On the Maintenance sheet, a display of both the number of records and data occupancy, as a percentage of the total allowed. These figures can be displayed for other size-types (1,3,4,6 or 9 Mb) that can accomodate the data present.
• The ability to create a copy of the database, but having a different size-type.
• A number of improvements and fixes affecting the displays and other functions.