* Date error on baptism entry

[johnmorrisoniom]

I have been using AS2 64bit for a while now.
If I have a baptism where I do not already have a birth year in, on the save screen I get a chance to enter an estimated birth date.
if I put in the same year as the baptism, there is an error message saying that this is later than the baptism, is this OK?
This occurs even for a December baptism.

Surely an estimation of the same year should be considered OK

ID:5908

[NickWalker]

Yes you're right - thats a bug and it will be fixed in version 3.0

Thanks

Nick

[Genie15]

This thread was in 2012 and the solution would be corrected in version 3.
Well, I'm on version 5 and have come across the problem of one Edward Kain born 18 Sep 1889 and baptised on 25 Sep 1889.
The information on Family Historian appears to be correct.
But get the error Baptism date is before Birth date. Which is incorrect.

[Jane]

Looking at the list the currently recorded Birth date is Q4 1889, so I suspect AS is comparing to the currently recorded date and not the date you entered.

[jbtapscott]

I'm sure Nick W will reply in due course, but my guess (based on my experiences) is that the Q4 date in FH is being used for the comparison.

[LornaCraig]

Did the error message appear before you entered the exact birth date in AS? The original posts were about AS comparing the two dates which were entered in AS itself, and that problem was corrected.

But perhaps the correction didn't extend to the comparison between the baptism date and the existing birth date in FH. As others have said, the Q4 1889 date may be the problem because it extends beyond the actual baptism date. However it's safe to ignore the warning if you are satisfied that your information is correct.

[NickWalker]

It's comparing the September baptism date with the previously recorded date of birth (October to December) and giving the warning. It's just a double check in case you're making a typing error and if what you're entering is correct then you can just ignore it. Nothing to do with the original issue reported in 2012 which was indeed fixed at the time.

Cheers

Nick