RootsWeb.com Mailing Lists
Total: 3/3
    1. Re: [BK] Why "invalid date"? Also quarters.
    2. Otto Jørgensen
    3. On Mon, 27 Feb 2012 08:29:21 -0000, "Malcolm Webb" <mfwebb2005@btinternet.com> wrote: >I have a large number of ancestors where I have recorded the birth, marriage >or death as "Qx YYYY", so I guess I shall be sticking to this format. > >I am grateful to those who have responded to my way of doing things; it has >made me test it out and leaves me satisfied that my method works (at least >for me) if not entirely accurately. I have an Idea, but I do not know if that is possible for John The accepted datevalue in BK is Format 0 (null) wharever Format 1 24-jun-1954 Format 2 24 jun 1954 Format 3 06/24/1954 Format 4 06-24-1954 Format 5 jun-24-1954 Format 6 jun 24 1954 Format 7 24-jun-1954 Format 8 24 jun 1954 Format 9 24-06-1954 Format 10 1954.06.24 Format 11 1954-06-24 Format 12 24.06.1954 If we are usib Qx instead of day-month and enter that, will i be possible for John to generate a date range we know Q1 = jan - mar Q2 = apr - jun Q3 = jul - sep Q4 = oct - dec So if you have made the correct setting in BK and and have e.g. set for use of 8 and add Q11954 that give as a result in Gedcom BET 1 JAN 1954 AND 31 MAR 1954 or in plain text between 1st january 1954 and 31th mars 1954 I think that will soved a lot of problem Additional the daterange can be used as the program have mention to be used in the present version. This will solve problem and give good result :) -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

    02/27/2012 03:04:56
    1. Re: [BK] Why "invalid date"? Also quarters.
    2. Malcolm Webb
    3. We already have the facility in BK to manually enter a date range e.g BET 1 Jan 1955 and 31 Mar 1955 which is handled properly in a GedCom. If John adds other formatting in BK to cope with quarters and convert them to a date range then those of us who do not wish to use the date range option would have no alternative. I do not like to see the date range option for births, marriages and deaths and so prefer not to use it -- hence I have opted to use Q1 1955 as a text string in a date box. The only time I use the date range option is for occupations and residences where I might like to see someone resident at the same address from 1861 to 1871, for example. All the best. Malcolm Webb mfwebb2005@btinternet.com <mailto:mfwebb2005@btinternet.com> -----Original Message----- From: bk-bounces@rootsweb.com [mailto:bk-bounces@rootsweb.com]On Behalf Of Otto Jørgensen Sent: 27 February 2012 09:05 To: bk@rootsweb.com Subject: Re: [BK] Why "invalid date"? Also quarters. On Mon, 27 Feb 2012 08:29:21 -0000, "Malcolm Webb" <mfwebb2005@btinternet.com> wrote: >I have a large number of ancestors where I have recorded the birth, marriage >or death as "Qx YYYY", so I guess I shall be sticking to this format. > >I am grateful to those who have responded to my way of doing things; it has >made me test it out and leaves me satisfied that my method works (at least >for me) if not entirely accurately. I have an Idea, but I do not know if that is possible for John The accepted datevalue in BK is Format 0 (null) wharever Format 1 24-jun-1954 Format 2 24 jun 1954 Format 3 06/24/1954 Format 4 06-24-1954 Format 5 jun-24-1954 Format 6 jun 24 1954 Format 7 24-jun-1954 Format 8 24 jun 1954 Format 9 24-06-1954 Format 10 1954.06.24 Format 11 1954-06-24 Format 12 24.06.1954 If we are usib Qx instead of day-month and enter that, will i be possible for John to generate a date range we know Q1 = jan - mar Q2 = apr - jun Q3 = jul - sep Q4 = oct - dec So if you have made the correct setting in BK and and have e.g. set for use of 8 and add Q11954 that give as a result in Gedcom BET 1 JAN 1954 AND 31 MAR 1954 or in plain text between 1st january 1954 and 31th mars 1954 I think that will soved a lot of problem Additional the daterange can be used as the program have mention to be used in the present version. This will solve problem and give good result :) -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON Remember - Use the Archives at http://archiver.rootsweb.ancestry.com/cgi-bin/search ------------------------------- To unsubscribe from the list, please send an email to BK-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

    02/27/2012 03:15:23
    1. Re: [BK] Why "invalid date"? Also quarters.
    2. Otto Jørgensen
    3. On Mon, 27 Feb 2012 10:15:23 -0000, "Malcolm Webb" <mfwebb2005@btinternet.com> wrote: >We already have the facility in BK to manually enter a date range e.g BET 1 >Jan 1955 and 31 Mar 1955 which is handled properly in a GedCom. > >If John adds other formatting in BK to cope with quarters and convert them >to a date range then those of us who do not wish to use the date range >option would have no alternative. > >I do not like to see the date range option for births, marriages and deaths >and so prefer not to use it -- hence I have opted to use Q1 1955 as a text >string in a date box. The only time I use the date range option is for >occupations and residences where I might like to see someone resident at the >same address from 1861 to 1871, for example. I know daterange are in the program and so it has been for years Q1 is a bbr. for English speaking countris. It is very similar to write win ter or spring, summer or autum. Neither of them are legal to Gedcom and makes error when exporting and importingto other langujage. So by that a coverting of q1, q2, q3, q4, winter, spring, autumn, summer are also good wayto have the same effect. I do understand that it is sometimes one want to express a date in that way. It is also th same as telling, "easter 1845" Can not be converted or translated to other language if using gedcom or not by copying database. It is the same problem if the users have different language. This was a proposal to John to solve a problem for some users around the warld. Date Range is a legal gedcom standard; Q1 is not -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

    02/27/2012 04:28:29