Re: [LegacyUG] a Warning, and another problem with the FAG

Search for the FAG id in a backup. Evert 2017-10-12 19:26 GMT+02:00 Dennis Murphy : > Perhaps I'm missing something as I had this happen only once so far. I > found it annoying that Legacy only lists the FAG memorial number without so > much as the Legacy RIN or at least the

Re: [LegacyUG] a Warning, and another problem with the FAG

Perhaps I'm missing something as I had this happen only once so far. I found it annoying that Legacy only lists the FAG memorial number without so much as the Legacy RIN or at least the name(s) of the individuals involved. This forces you to exit Legacy, go to FAG site then plug in the listed

Re: [LegacyUG] a Warning, and another problem with the FAG

In Legacy 8 I was adding the number to source detail, and in Version 9 I still do this as well as the spot for the number on the individual's page.  Since this mistake usually happens when I and working with a particular family group, I simply check the rest of the family members that do not

Re: [LegacyUG] a Warning, and another problem with the FAG

Its is removing data that I rely on to keep my data base accurate, Good programmers never remove data!!! They may divert it as legacy does when you merge data fields and they move one to and event but never never destroy data that a client inputs. On Thu, Oct 12, 2017 at 9:05 AM, Henry T.

Re: [LegacyUG] a Warning, and another problem with the FAG

Duplicate memorials should be corrected and So when I find one and report it, I mark down the numbers in Notes. I choose the most likely to survive (Using FAG rules) and mark that one in the legacy field. Ian On Thu, Oct 12, 2017 at 8:37 AM, Donna Newell wrote: > What

Re: [LegacyUG] a Warning, and another problem with the FAG

I agree with all that you say, but They should never destroy data that I input. And By disassociating the name from the number I no longer know which person has been left off. On Thu, Oct 12, 2017 at 5:43 AM, Henry T. Peterson Jr. wrote: > *Ian* > > > > *My two cents…. I have

Re: [LegacyUG] a Warning, and another problem with the FAG

I have had the same experience… the ‘duplicate’ number is deleted with no reference. I find that very annoying. Perhaps it won’t happen again but it certainly would have been nice for the program to alert me and let ME make the decision or, at the very least, let me know which name had the

Re: [LegacyUG] a Warning, and another problem with the FAG

Legacy isn’t removing individual information. It is only removing duplicate FAG numbers. Henry From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Donna Newell Sent: Thursday, October 12, 2017 7:37 AM To: Legacy User Group

Re: [LegacyUG] a Warning, and another problem with the FAG

What if it isn’t a typo? People go in occasionally to FAG and add a duplicate memorial, when it is discovered one of them is removed, it could be the one that you are citing. I have had it happened to me occasionally. Annoying, but ok for me because I am putting the number in the description

Re: [LegacyUG] a Warning, and another problem with the FAG

Ian My two cents…. I have over 13,000 FAG memorials in my database and most of the time they are entered by copy and paste (I use two monitors while entering data). I for one am grateful that “File maintenance – check/repair” catches these errors.. otherwise they would go undetected and be

[LegacyUG] a Warning, and another problem with the FAG

I would very much like the FAG numbers to be unique, however the current situation where if you have a duplicate number and run "File Maintenance" you get a message that says Duplicate Find a Grave IDs have been found. You will need to re-add the Find a Grave ID back to the individual the ID