There is an ascending order of solutions we try whenever there is a
problem new to us or whose solution is not listed in our technical
support pages. Usually one of them will fix the glitch (most people
will never have to go beyond Step 4). Here are the steps,
beginning with the easiest and most basic things to do:
1. Run File Maintenance - Check/Repair (File
Maintenance > Check/Repair). Next try Legacy again.
2. If the error persists, export your records into a new
Legacy family file, which you should use:
A. Click File on the menu bar and select Export To
from the file menu.
B. Choose Legacy File from the submenu and proceed.
C. Give the file you will export to a new name and click Save.
D. The Export screen will open. Please click the large Start
Export button. (If you get a message about sources, click Don't
Assign a Source.)
E. Next try Legacy again using the new file and delete the old
one when you are satisfied with the results.
3. If a Legacy family file is so damaged that Steps 1
can't repair it, then restore the file from your most
recent backup copy.
You should make regular backups and test
them. Please visit www.legacyfamilytree.com/tipsBackups.asp
for step-by-step instructions.
See Step 10 if you can't repair your family file in Legacy
nor restore it from a backup copy.
4. Repair the program by updating Legacy 8.0. Updates
are patches and enhancements that fix bugs, replace damaged/missing
files, and bring your program up to date. Click
here for more information.
5. Delete from the Legacy folder on your hard drive all
files that end with a .USR and .DBM extension. Go to step 6
(reinstall). After restarting Legacy, you will need to reset any
customized settings you made.
6. Reinstall the Legacy.
If you re-install from a CD, you should also update your program
(see Step 4). If you are using Legacy Deluxe you may
need to re-enter your Deluxe Customer Number in the program (click on
Help and select Unlock Deluxe Edition and follow the
7. Please download and install Microsoft Data Access
Components [MDAC] 2.7 RTM (English)*
MDAC 2.7 contains the same version of the MDAC components that
are installed by Windows XP and is supported on Windows 98, Windows
ME, Windows NT 4 and Windows 2000. To download the MDAC 2.7 please
8. Please download and install Jet 4.0 Service Pack from
The service pack solves several errors reported by Legacy users. There are
two versions of the Service Pack; please choose the
that matches your Window's operating system. There are two steps
involved: downloading and running the file installation.
For Computers That Are Running Microsoft Windows 95, Microsoft
Windows 98 and Microsoft Windows NT version 4.0
Use Jet40SP8_9xNT.exe to install Jet 4.0 SP8 on
computers that are running Windows 95, Windows 98 or Windows NT
- For Computers That Are Running Windows Millennium Edition
Use Jet40SP7_WMe.exe to install Jet 4.0 SP7 on computers
that are running Windows Millennium Edition:
- For Computers That Are Running Microsoft Windows 2000
Use Windows2000-KB829558-x86-ENU.exe to install Jet 4.0
SP8 on computers that are running Windows 2000:
- For Computers That Are Running Microsoft Windows XP
Use WindowsXP-KB829558-x86-ENU.exe to install Jet 4.0
SP8 on computers that are running Windows XP:
9. If the error is caused by a damaged, out-of-date, or
missing file (you will get a message about it), let us know which file
and we will send a replacement file as an e-mail attachment with
directions. Please contact Support@LegacyFamilyTree.com.
10. If you don't have a viable backup and your Legacy family file is damaged beyond what the
program's Check/Repair utility can fix, open the family file in MS Access 2000*
and run Tools > Database Utilities > Compact and Repair
Sometimes a damaged family file can be opened in Access, but the Compact
and Repair utility won't fix the family file problem so that it
can be used in Legacy. In this instance, re-open the family file
in Access and click on Tools > Replication > Create a
Replica.... This will clone a new file named Replica of
_________.fdb, where the underscore is the name of your family
file. Next rename your family file and make certain that the
extension is changed to .fdb and try it again in Legacy.
If you do don't have MS Access 2000, please send the
family file to us to attempt a repair. Contact
for further information.
11. Make certain that that have downloaded and installed the
latest Windows patches and services packs for your operating system.
Go to www.microsoft.com to
check for the most current Windows updates.
12. Run a system diagnostic and repair tool, such as Norton
WinDoctor, to fix problems that can occur in the Windows operating
system. System diagnostic tools in many instances will find and repair
problems with Windows system files and drivers, shared files, Registry
errors and applications that won't launch.