You can turn off the red 'invalid date" - options - dates I use cir/abt/bef/aft with no problem cir 1890 {no ___ or ---) Also 30 Mar 1851 - 31 Mar 1851 or 30 - 31 Mar 1851 both work Fran The Future is as Great as the Promises of God On 21/02/2012 5:32 PM, J. P. Gilliver (John) wrote: > I know an event is between 30 and 31 March 1851, so I enter > > 3_031851 > > (I have ddmmyyyy selected as _entry_ format for dates). BK correctly > converts it to > > 3_ Mar 1851 > > (I have that format selected for date _display_ format). > > But BK also says in red "Invalid date". > > What gives? > > (Similarly, "CIR ____1812" gets correctly converted to "CIR __ ___ 1812" > but is also flagged as "Invalid".) > > Also, if I know something happened in the fourth quarter - i. e. month > 10, 11, or 12 - and I enter the date as "__1_1666", it gets converted to > "__ Jan 1666". (__0_1666 - for any of the other three quarters - comes > out as __ ___ 1666, which is perhaps OK.) Ideally I'd like a way of > recording a quarter. (Currently, I just put "Q4" [or whatever] in the > notes field for that event, but would be interested to hear what others > do, or any suggestions.)

In message <BLU0-SMTP5234A0B84DA3D08C2DCD0DE3640@phx.gbl>, Fran LaChance <singer.35@hotmail.com> writes: >You can turn off the red 'invalid date" - options - dates (I didn't know that - I'll look into it.) >I use cir/abt/bef/aft with no problem   cir 1890 {no ___ or ---) I use CIR/ABT/BEF/AFT too, but if you don't enter four digits (even of some of them are "_"), doesn't the string remain as a string, whereas if it's entered fully, get handled as a date, so for example is used in calculation of a person's (approximate) age? > >Also 30 Mar 1851 - 31 Mar 1851  or 30 - 31 Mar 1851 both work [] The first option would work. -- J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf "I do not feel obliged to believe that the God who endowed me with sense, reason, and intellect intends me to forego their use". - Gallileo Gallilei