Brian: I created a new event called "Tombstone" which I use frequently with an attached picture. Normally the Tombstone is not present when a person is buried, but is installed later (I know there are exceptions). I will normally use a date of a week or so later if I don't know when the Tombstone was placed.
Of course, this shows up in the potential problem areas for these Tombstone events. My solution was to Edit the Master event (go to View, Master Lists, Event Definition & Edit the Event Definition) and Turn Off of the Potential Problem List simply by checking the box to "Exclude from Potential Problems Report". Once I have done that, my special event, "Tombstone", no longer is shown in any of the Potential Problem Reports or Red circles regardless of what date I use for the Tombstone event. I would think you could do that for the Cemetery Event and then you will not have any problems going forward. Your example of the Census event being 22 Jan 1920 and you have his death Aft 1 Jan 1920 should always appear in the problems report. I would think you would correct the death date to be Aft 23 Jan 1920. You have hard evidence that he was alive on 22 Jan 1920, so creating a death event before 22 January 1920 should always return a potential problem -- it seems obvious that one of the dates is incorrect and should be corrected. Leon Chapman On 12/10/14, 12:52 PM, Brian L. Lightfoot wrote: > OK, a little more resolution on the problem after staying up half the night > comparing various individuals and events. I've mostly ignored the problem > indicators for the past few months until now figuring that I'd eventually > handle that task. Anyhow, what I now see is as Brian in Support had indicated > that some events are hard coded to not generated a date error. It seems these > events are BURIAL and OBITUARY which makes sense as usually the burial is > after the date of death. :-) But now on to the problem events that could > generate a date error after death. These include a Census Event and a > Cemetery event. There may be others depending upon how or what the user > creates. > > I have opted to use the date on the census event as the date that the > enumerator actually visited the household and it’s the date that is entered > on the census form. The error "Event date is out of range" will occur on a > person's last Census Event. For example, if I have no exact date of death for > a person but he was listed on a 1920 Census, I will enter his date of death > "After 1 Jan 1920" (assuming that he was born at least 100 years ago), which > is the date that census was supposed to represent of who was alive and lived > at the residence on that date. However, the actual Census Event that I create > is dated "22 Jan 1920" which was the date of the enumerator's visit. You'd > think that "AFTER" would mean just about anything after a date but it looks > like Legacy assumes anything that is AFTER a date of death to be "out of > range" --- anything other than a Burial date or an Obituary date. There are > some older German Census records in which deceased persons were listed. Don't > ask me why they did that but in each of those cases, an "out of range" error > would also be generated if the census was after the date of death. > > Now the important thing here is to not argue the validity of using the > enumerator's date of visit for a census or how to properly handle the German > deceased persons on a census, but to look at the functionality of the option > to exclude "Events or Facts after a death date" which generate errors. With > that box NOT checked, no error should be generated, yet Legacy is indeed > showing a date error. Am I wrong in thinking that is a bug? > > An example of the last Census Event error goes like this: > DIED: Aft 1 Jan 1920 > 1920 Census Event; Date 22 Jan 1920 (date out of range error generated) > > > Another event that I create is CEMETERY. I use it to show descriptions about > the gravestone, FAG memorial numbers, photos of the gravestone, and other > details rather that use the BURIAL Notes or Address tabs. I find it a lot > easier to search for and create lists of burials within a specific cemetery. > However, this user created event called Cemetery needs a date and so I enter > that same as the BURIAL date. There are even a few cases of where the > deceased person was re-buried a few years later in a different cemetery which > would require a date different than the original hard coded BURIAL date. In > either case, this user created event of CEMETERY will generate a date out of > range error. And once again, the setting of excluding events or facts after > the date of death has no effect. > > An example of the Cemetery error goes like this: > DIED: 28 May 1926 > BURIED: 31 May 1926 (no date error) > OBITUARY: 7 Jun 1926 (no error) > CEMETERY: 31 May 1926 (date out of range error generated even though it’s > the same as the BURIAL date which was not out of range; my settings are to > exclude Events and Facts after death date) > > Bottom line: It's not really a major problem and doesn't affect report > generation. I can continue to ignore these types of problems. Hopefully some > future update will take a look as why the exclusion setting is not working or > maybe make sure Census Events are hard coded to be excluded. > > > Brian in CA > > > > -----Original Message----- > From: Brian/Support [mailto:br...@legacyfamilytree.com] > Sent: Tuesday, December 09, 2014 2:43 PM > To: legacyusergroup@LegacyUsers.com > Subject: Re: [LegacyUG] Potential Problem Checker > > Some events are hard coded so they will not generate a potential problem as > an event after death because they always occur after the death date. > The programmers did some work in the last little while on those. The obituary > is one of those that may now be in the hard coded not a problem list. > > Brian > Customer Support > Millennia Corporation > br...@legacyfamilytree.com > http://www.LegacyFamilyTree.com > > On 09/12/2014 12:06 PM, Kelly Booth wrote: >> I just >> installed the latest update 2 days ago. This morning, I added 3 new >> obituaries and noticed that the icon that comes up when you put in a >> date after the death was not there. I double checked my dates to >> verify the obit dates were after the death dates and I did not have >> them marked to be excluded. I ran the potential problems report and they >> did not appear there either. This was working prior to this last update. > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > 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 > > -- ************* *Dr. Leon D. Chapman* ch...@cox.net 623-398-8900 www.scgrandgolf.com ************* Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
