Well, I put "spring of 1991" back before a forced the date to be a fixed tpype format. I would not do that today. I would have put 1991 in the date and then the note might say it was in the spring. In other words, I am trying to force all to put proper dates in the date field. Ver 3 will be even stricter: the date MUST be a valid date (like the UCC accepts) as internally the date will be stored as a series of numbers - day number, month number, year number, cycle number, etc. Ira At 06:34 PM 2/27/98 +1100, you wrote: > >G'day Ira et al, > >I am seem to have a minor annoyance in trying to use "non-standard" dates in >events. > >Here is a quote from the help file on "Event Editor - Standard":- > >Business Startup: Ira Johan Lund started a business in the spring of 1991 at >Clarksville, Montgomery, Tennessee called Cumberland Family Software. > >I have examined the SAMPLE database and this is what appears from the "same" >(?) event:- > >Ira Johan LUND started a business 1991 at Clarksville, Montgomery, Tennessee >called Cumberland Family Software. > >I tried to modify the date used from "1991" to "in the spring of 1991" but >the entry is too long so I created my own "non-standard" date - "late >1950s" - here is the result:- > >Michael CALDER late 1950's AD started playing lawn bowls. > >Not worrying about the grammar it is the "AD" that is the problem. Any >"word" attached to a date in the "date window" will trigger the addition of >AD (or you can choose BC). > >Can we have a "blank" option? so that we can have dates like "early 1856" >"mid 1950s" or even a bigger field to add "in the spring of 1991" <VBG>? > >HURU Mike > ---------------------------------------------------------- Ira J. Lund Cumberland Family Software, Clarksville, Tennessee, USA Genealogy Software for Beginners and Professionals E-mail: ira.lund@cf-software.com http://www.cf-software.com