3022 Can't have duplicate key; index changes were unsuccessful -- Please try the following solutions: Perform File Maintenance to see if it will solve this problem. File Maintenance will repair index errors, correct common record problems, remove references to unused information, and compacts the family file. Here are the steps: 1. Click File from the menu bar and select File Maintenance from the file menu. 2. Choose the Check/Repair option from the submenu and proceed. If that does not fix the problem, next export your records to a new Legacy family file. Here are the steps: 1. Click File from the menu bar and select Export To from the file menu. 2. Choose the Legacy File option from the submenu and proceed. Please let me know if you have any further questions. Jim Terry Technical Support Millennia Corporation www.LegacyFamilyTree.com ----- Original Message ----- From: "Wendy & Mal Lavender" <[EMAIL PROTECTED]> To: "Legacy User Group" <[EMAIL PROTECTED]> Sent: Monday, January 08, 2001 2:09 PM Subject: [LegacyUG] A Friend in Need My very good friend running Legacy 2 has recently downloaded Ver. 3 and now finds that she gets Error Saving History 3022 The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again. I suspect that she should have run the File Maintenance before her last backup and uninstalling all the Legacy software. Is there anyway she can work around this problem, please as she's unable to open the database to check the file? Wendy Lavender Toormina, south of Coffs Harbour, NSW AU
