tag:blogger.com,1999:blog-5512311610334754148.post1828278607871713579..comments2023-04-20T12:46:11.858-06:00Comments on The Ancestry Insider: Darned Posthumous MarriageThe Ancestry Insiderhttp://www.blogger.com/profile/02490682912125335188noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5512311610334754148.post-84272499504407522132015-03-21T09:34:53.216-06:002015-03-21T09:34:53.216-06:00When you commented parenthetically, "(Let’s s...When you commented parenthetically, "(Let’s see how your tree program likes a marriage date after a death date! Or maybe you use one of those programs that doesn’t care, no matter how bad your data is.)" , I immediately thought, "Yes, like FamilySearch Family Tree, which accepts all dates no matter how ridiculous." Just to make sure I wasn't falsely accusing FSFT of such practice, I logged on, found a relative with no marriage date entered and entered a date after the death of the wife. It accepted it, no questions asked. This has always bugged me. I am not a professional programmer, but I do have some experience writing programs that my chemistry students used. It was easy to program checks for impossible answers that notified the student of the problem. I suspect it would be just as easy for FamilySearch software engineers to do the same for the Family Tree software. Why don't they to it? Do you have any idea? It really gnarls me that FamilySearch Family Tree is one of "those programs that doesn't care". Oh, and in case you are wondering, I deleted the false marriage date after seeing it was accepted uncritically.Johnhttps://www.blogger.com/profile/00448728584336207199noreply@blogger.com