Hi: IF I don't have a birth day but do have a baptism/christening date, the fact type CHRISTEN will print on reports in the birth field. Similarly if I do not have a death date the BURIAL will print on those same reports. BUT, if I don't have a MARRIAGE, but I DO HAVE a 'marriage contract' date ... THAT does not appear at least on the screens for the family . IS there a 'replacement' fact type that would print / show in this case??? Pat Mc

Hi Pat, If I only have the marriage intention date, I use that either with "abt" in front of the date or perhaps that intention date with "aft" before the intention date in the marriage field. Then I may put the intention or contract date in the marriage note. In general I use a lot of estimated dates when I do not have actual dates for birth & marriage fields. That helps keep one from mixing up generations, as one finds frequently when they query the LDS FamilySearch through Rootsmatic for clues. Something that you did not ask, but by accident I find that Bruce has included "by" as a modifier we can now use for estimated dates. I used to be frustrated when transcribing from books that I had to use "bef" when the book had "by". There is one downside to using estimated dates at time of data entry. RM will not necessarily pick up a duplicate that it might have caught, had I not used estimated dates. That is a choice I frequently make in entering new data. -----Original Message----- From: Pat McGrath via Hi: IF I don't have a birth day but do have a baptism/christening date, the fact type CHRISTEN will print on reports in the birth field. Similarly if I do not have a death date the BURIAL will print on those same reports. BUT, if I don't have a MARRIAGE, but I DO HAVE a 'marriage contract' date ... THAT does not appear at least on the screens for the family . IS there a 'replacement' fact type that would print / show in this case???