For quite some time I have noticed that the LDS Baptism and Confirmation locations default to the wrong setting. This is happening also with data pulled from Family Tree with LegacyFS. If one of those ordinance dates is during the life of the individual, then the "Live" button should be set. If done after the death of the individual then the "Temple" button should be set. If done prior to age 8 of the individual or after the current date it is an error and should probably be detected by Potential Problems in the LDS tab. Likewise, the incorrect location setting should be reported in the LDS Potential Problems. The following SQL scripts only fix ordinances that have dates recorded.
More work is needed to 1) identify sealings that were done for children that should have been recorded as BIC. 2) sealed to parents without having the parents sealed as spouses. 3) detect ordinances done before age 8. 4) ordinances performed the same day in different temples. 5) several other combinations that might prove beneficial to report in Potential Problems. This SQL script will correct the "Live" Baptism if birth and death dates are recorded. UPDATE tblIR SET tblIR.BaptismKind = 0 WHERE tblIR.IDIR>0 And tblIR.BirthSD>0 And tblIR.DeathSD>0 And tblIR.BaptismSD>tblIR.BirthSD And tblIR.BaptismSD<tblIR.DeathSD And tblIR.BaptismKind=1; This SQL script will correct the "Live" Confirmation if birth and death dates are recorded. UPDATE tblIR SET tblIR.ConfirmationKind = 0 WHERE tblIR.IDIR>0 And tblIR.BirthSD>0 And tblIR.DeathSD>0 And tblIR.ConfirmationSD>tblIR.BirthSD And tblIR.ConfirmationSD<tblIR.DeathSD And tblIR.ConfirmationKind=1; This SQL script will correct the "Temple" Baptism if death date is recorded. UPDATE tblIR SET tblIR.BaptismKind = 1 WHERE tblIR.IDIR>0 AND tblIR.DeathSD>0 AND tblIR.BaptismSD>tblIR.DeathSD AND tblIR.BaptismKind=0; This SQL script will correct the "Temple" Confirmation if death date is recorded. UPDATE tblIR SET tblIR.ConfirmationKind = 1 WHERE tblIR.IDIR>0 AND tblIR.DeathSD>0 AND tblIR.ConfirmationSD>tblIR.DeathSD AND tblIR.ConfirmationKind=0; If BaptismKind=0 then IDTRBaptism points to the Location Record in tblLR If BaptismKind=1 then IDTRBaptism points to the Temple Record in tblTR If ConfirmationKind=0 then IDTRConfirmation points to the Location Record in tblLR If ConfirmationKind=1 then IDTRConfirmation points to the Temple Record in tblTR I did not find any of the location pointers in error in my databases but there is a possibility for that error. The SQL scripts might include tblIR.IDTRBaptism = 1 or tblIR.IDTRConfirmation = 1 to clear erroneous ordinance locations when Live is switched to Temple or vice versa. Then the location would have to be re-entered if possible. These scripts corrected over 35,000 of these errors in my large database so the problem is significant. Ron Taylor 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
