I enter using dd-Mon-yyyy Jan Feb Mar, etc. for month. I find using ddmmyyyy can sometimes provide incorrect data if interpreted by those on opposing sides of "the Pond." Europeans tend to use dd/mm/yyyy, while many Americans use mm/dd/yyyy. Jared > (For the avoidance of doubt, I use the ddmmyyyy format.) > > In message <[email protected]>, Jared > Handspicker via <[email protected]> writes: >>Sorry if this comes across as redundant. >> >>When I have quarters to enter, often with UK registration of birth dates, >>I simply put the year, and expand on the quarter in notes. One of the > > Yes, that's what I do. Since it's almost exclusively UK BMD > registrations where I only know the quarter, I put CIR if it's the first > one (when I remember). The single-digit wildcard doesn't work: fourth > quarter is months 10, 11, and 12, but entering __1_yyyy gets translated > to January (and IIRR __0_yyyy doesn't work either). > > The shortform date entry - ddmmyy for (roughly) 20th century dates - > doesn't work with lots of (possibly any?) wildcards: I can't enter > ____60 and get __ ___ 1960, for example. Or ____6_. > [] >>What I have had trouble with, and again, ended up using explanatory >> notes, >>instead, is when I have the right day and month, but the years "range." >>Such as individuals known to be born on 05-Mar-191X (1912, 1914, 1917, >> or >>1919, depending on the record). Listing 1912, and commenting in the >> notes >>that the date could be any of the others, is a relatively safe way of >>being as accurate as possible. > > Have you tried _ instead of X? > [] >>> It seems that BK allows us to be flexible even though the red warning >>> notices come up. It would be good to have a distinction made in >>> Brother's >>> Keeper between Invalid dates and Incomplete dates. Others on this >>> forum >>> have made that point too. That way people would understand better why >>> the >>> warning messages come up. > > I'll add to the plea/request though (-: >>> >>> Andrew Jackett of New Zealand. >>> >>> >>> Andrew Jackett of New Zealand. > [] > -- > J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)[email protected]+H+Sh0!:`)DNAf > > "I hate the guys that criticize the enterprise of other guys whose > enterprise > has made them rise above the guys who criticize!" (W9BRD, former editor of > "How's DX?" column in "QST") > Remember - Use the Archives at > http://archiver.rootsweb.ancestry.com/cgi-bin/search > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the quotes in > the subject and the body of the message > ------------------------ Jared "Jed" Handspicker Usque Saeculis Vigilem

On Tue, 16 Jun 2015 18:00:28 -0400 (EDT), Jared Handspicker via <[email protected]> wrote: >I enter using dd-Mon-yyyy Jan Feb Mar, etc. for month. I find using >ddmmyyyy can sometimes provide incorrect data if interpreted by those on >opposing sides of "the Pond." Europeans tend to use dd/mm/yyyy, while >many Americans use mm/dd/yyyy. > In Norrway we recomend ddmmmyyyy thats giv 1814 may 1814 17 may 1814 Som put ?? xx 00 and other figure in date field. Thats makes trouble -- Otto Jørgensen http://home.online.no/~otjoerge/ All email is checked by NIS2014