Hi,
I just tried entering Mar 1723/24
Entered like that - no trouble with the date checking
Enter as 3 1723/24
and you get the invalid date
Enter as 3 1724 and it changes to Mar 1723/24
I agree it should be changing to Mar 1724/25 as you are more likely
to be finding the date in the Old Style than the New.
Came through Potential Problems check with No Problems found.
Cathy
At 07:56 14/09/2005, you wrote:
Thanks for your suggestion, but I think I'll just continue doing it as a
double date and mark it to exclude from the potential problems.
la Nell
-----Original Message-----
Subject: RE: [LegacyUG] V6 Potential Problem reports - Check for valid
dates
La Nell
By just typing "feb 1724" or "2/1724" the date will be correctly recognised
and you shouldn't get an entry in the potential problems.
Not certain about all your existing data, but the entries I used to have
marked as "invalid" aren't flagged now.
It still annoys me that you have to type 1724 to get a date that was, at the
time, 1723. So when entering data from a Parish Register you have to
remember to add one to the year if the date is before 25th March.
Jack
Subject: RE: [LegacyUG] Potential Problem reports - Check for valid
dates
I use DD MMM YYYY format with the double dating checked. What I am trying
to achieve is the year 1723/4 double date with the month as Mar and no day.
I am not trying to set it as between the years of 1703 and 1704 but as a
double date. It shows correctly as "Mar 1723/4" on the family page and on
reports, but the "report all questionable dates" sees it as an invalid date.
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
