I don't think the RIN change of some of the records (only a few, as far as I can see) has materially affected the errors, but it did point up to me that the errors have not only occurred to the most recently-input data.
Having today also sent my long email direct to Legacy Technical Help as part of an ongoing conversation, I received this reply; "I can't predict what may happen with Legacy on your computer. At this point I think the best solution is to restore your family file from a good backup copy. For detailed backup and restore guidance with helpful screen shots please visit http://www.legacyfamilytree.com/helpLegacy7Backup.asp";. I had already explained that, as this seems to be a long-term problem that I have only just managed to tie down, my regular backups of course also contain the errors. Having recommended Legacy for years, I am rapidly losing any confidence. It seems from this thread that the new SourceWriter may also be affected in other databases, but that Legacy don't seem to be doing much to solve the general problem, or mine in particular. Paul --- On Fri, 15/10/10, Ron Ferguson <[email protected]> wrote: > From: Ron Ferguson <[email protected]> > Subject: Re: RE: [LegacyUG] Citation Detail Loss > To: [email protected] > Date: Friday, 15 October, 2010, 17:55 > Paul, > > Are you saying that the change in the number of the RIN is > an error and you > don't know whether to correct , or that correcting the > citation error > changed the RIN or what? > > The actual value of the RIN makes no difference to any > thing other than > Pedigree web pages where the file name is the RIN . The > odds are that when > you imported the GEDCOM you did not set it to not change > the RINs. > > Have you reported the problems as a bug? > > Ron Ferguson > http://www.fergys.co.uk/ > -------------------------------------------------- > From: "Paul Underwood" <[email protected]> > Sent: Friday, October 15, 2010 3:19 PM > To: <[email protected]> > Subject: Fw: RE: [LegacyUG] Citation Detail Loss > > > > > As a last resort last week, I exported a Gedcom of my > database, and > > reimported it to a new Legacy Standard installation. > This appears to have > > had the effect of renumbering some, but not all, of > the RINs which do not > > necessarily now run in date of input order. The errors > however tend to > > occur in clusters of RINs. > > > > I am now in the situation where I am unsure whether to > correct the errors > > or not – will this cause further overwriting / > leakage elsewhere? Either > > way, I now find it difficult to trust Legacy. > > > > I recommend others should check their Citation Details > to see if a similar > > 'hidden' bug exists widely or if it's just me and one > other. > > > > Paul U > > > > > > 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 > > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
