Just a reminder to those creating Legacy webpages, especially the Pedigree pages. Legacy uses the RINs as the file name in the case of the latter, so changing the RINs will ruin all your well earned search engine ranking points, the bookmarks others may have made to your pages will no longer work, and if your file is large and comparison software used for updating then your day will be nicely ruined as well.
Ron Ferguson http://www.fergys.co.uk/ From: Jay 1FamilyTree Sent: Saturday, November 30, 2013 1:28 AM To: [email protected] Subject: Re: [LegacyUG] please do "check/repair" regularly After editing my file, before I shut down, I Re-number and unused RIN's and then the same for MRIN's Then run file check (Once a week run clean up and Compact) Then I run the backup (And on the First of the Month the backup includes media) Afraid to say that at least a dozen times in the last 10 years I have been so thankful I have the same routine. But as Jack mentioned, running File Check regularly will keep things in order. Jay On Fri, Nov 29, 2013 at 4:39 PM, Jack Earnshaw <[email protected]> wrote: I have used Legacy since V3 and have done File Maintenance/Check & repair from time to time. But this obviously wasn't frequently enough as my file became corrupted and wouldn't open. I was lucky in that Michelle in support was able to repair the file, but this might not have been possible. I had used V7.5 of the program to update some records based on a new source of data becoming available. Before closing the program I did a backup. However, this wasn't enough!!!!! I downloaded V8 Basic version and then used V7.5 to try to make a copy of my main file. The system reported that my file wasn't in the correct format and crashed Legacy V7.5 I did a restore from 21 Nov, the date of the last updates, and the program again said the file was corrupted. A restore from a 16 Nov backup produced a usable file. Having reported the problem, I was asked to send my file to Millenium and within a few hours a repaired version of my 21 Nov file was sent back to me. I opened the restored 16 Nov file and the repaired 21 Nov file and the number of individuals and families differed by a small number, but greater than expected. I did a Search on the "added dates" of individuals and marriages and the number altered was, as expected, a much lower number than had been reported by the program. After receiving my repaired copy I then did a "check/repair" on the backup copy from the 16 Nov backup. Several errors were reported and so I repeated the check/repair and no errors were reported. Afterwards the number of individuals and the number of families had altered and was totally in line with what I had done on 21 November. So, the file was already corrupted BUT WORKING when I made the last updates and did a backup. The moral is that I should have carried out a check/repair at an earlier date. The fact that I could still open the file didn't mean that everything was OK. Thanks to Michelle in Support I haven't lost any data, but it could have been much worse. I will now do a check/repair much more often and, of course, make backups after each time I change my data. If I had done the check/repair sooner then I might not have needed to ask Support for their help to repair my file. Jack Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
