We are aware of the Access Violation problem in Legacy FamilySearch that some users experience. There is no one cause. Sometimes it happens when a button is clicked while another action is still being processed. Often it will not repeat.
Copy DAO360.DLL from the C:\Program Files
(x86)\Common Files\microsoft shared\DAO folder into the
C:\Windows\SysWOW64 folder and the C:\Windows\System32 folder. This should fix the problem. Make sure Legacy is closed when you do this and your
computer will probably ask for Administrative approval, so give it. For
most users, Legacy Family Tree and Legacy FamilySearch will work at
this point, so stop here. You are done.
If the problem persists, please apply these steps in the order given.
1. Click OK and hopefully everything should behave as expected. Try what you were doing in Legacy FamilySearch again. If the problem persists, go to step 2.
2. Click the Refresh button on the right side above the FamilySearch person and then click the Reload button to reload your Legacy person. Sometimes Legacy FamilySearch is holding on to old data and this will clear it out.
3. Close Legacy FamilySearch and open Legacy Family Tree.
4. Run File Maintenance - Check/Repair. Click on File> File Maintenance > Check/Repair and follow the prompts. If the error messages occur during the Check/Repair process, click No to continue with the repair. Do step 1 twice if errors are found.
5. Open Legacy FamilySearch and if you are able, click on File > File Maintenance > Check and Repair.
6. Try what you were doing in Legacy FamilySearch again. If the problem persists, go to the next step.
7. Close Legacy FamilySearch and Legacy Family Tree. Next browse into the Legacy folder on your hard drive and right-click on the FamilySearch folder, then select Rename from the popup menu and rename the folder zFamilySearch.
For 32-bit Windows OS C:\Program Files\Legacy8\zFamilySearch
For 64-bit Windows OS C:\Program Files (x86)\Legacy8\zFamilySearch
8. Next update your Legacy program by visiting http://www.legacyfamilytree.com/DownloadUpdate.asp, which will create a new FamilySearch folder.
9. If none of these steps work, the Access Violation error might be fixed with clean re-installation of Legacy.