The temporary backup isnt a zip file. The backup through File > Backup Family File is a zip file.
And you all don't realize how we'd *love* to figure out what's going on! We can't find a pattern of what users are doing, which version of Windows they have or anything that can give us a clue. It works fine for us. Thanks for using Legacy. Sherry Customer Support Millennia Corporation supp...@legacyfamilytree.com http://www.LegacyFamilyTree.com We are changing the world of genealogy! When replying to this message, please include all previous correspondence. Thanks. --------Original Message------------- From: k...@legacyfamilytree.com [mailto:k...@legacyfamilytree.com] On Behalf Of CE WOOD Sent: Wednesday, March 11, 2009 10:13 AM To: LegacyUserGroup@legacyfamilytree.com Subject: Re: [LegacyUG] Exporting to a new Family File Okay, it's not the only solution, but it is the final solution, and it doesn't work. Legacy has no problem making a temporary backup before a Manual Merge, but has Error 91 when doing a zip BackUp. If only there were a way to save the temporary backup. Has Legacy looked into the zip program? Something in there might be triggering Error 91 since making the temporary backup has no problem (so far). Carolyn ----- Original Message ----- From: Sherry/Support To: LegacyUserGroup@legacyfamilytree.com Sent: Wednesday, March 11, 2009 7:45 AM Subject: RE: [LegacyUG] Exporting to a new Family File No - it's not the only solution. The first solution is to make sure you have the latest update. The second solution is a File > File Maintenance > Check/Repair. If that doesn't work, *then* you export to a new Family File. As explained to me by Ken, a *new* file is created when you export. Therefore, information in that new file is added the date of the creation of the new file. But possibly the programmers may be able to give us the option to retain what's lost or changed with the export, but the key word here is "new". Not "copy" but "new". Thanks for using Legacy. Sherry Customer Support Millennia Corporation supp...@legacyfamilytree.com http://www.LegacyFamilyTree.com We are changing the world of genealogy! When replying to this message, please include all previous correspondence. Thanks. --------Original Message------------- From: k...@legacyfamilytree.com [mailto:k...@legacyfamilytree.com] On Behalf Of CE WOOD Sent: Wednesday, March 11, 2009 1:19 AM To: LegacyUserGroup@legacyfamilytree.com Subject: Re: [LegacyUG] Exporting to a new Family File Oh please do! Exporting to a new file is Support's only, but ineffective solution, to fixing the infamous Error 91 which occurs so often when trying to back up the Family File. So many files have been stripped as a result, all to no avail. Your suggestion would be most welcome. Carolyn ----- Original Message ----- From: Ron Taylor To: LegacyUserGroup@legacyfamilytree.com Sent: Tuesday, March 10, 2009 10:42 PM Subject: Re: [LegacyUG] Exporting to a new Family File I was glad to see that others have encountered this problem when moving data to another legacy file. Definitely, there should be an option to retain the modified and added dates when moving. Also the indicator as to whether the data was imported or hand entered should be preserved...perhaps again by option. It is important to me to know when the data was originally added or last modified and if it was imported. With the current program those items are lost when the file is exported to another legacy file. If no one has yet submitted it, I will soon. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
