In that case, I believe the correct accepted genealogy term is "removed." Sam Smith in March 1897 removed from Pennsylvania to Ohio. In 1899 Sam Smith removed from Ohio back to Pennsylvania. And so on. Rick Beitler If there are no dogs in Heaven, then when I die I want to go where they went. ~ Will Rogers & Rick Beitler -----Original Message----- From: Bill via Sent: Thursday, March 19, 2015 3:10 AM To: J. P. Gilliver (John) via Subject: Re: [BK] New Event But these people aren't either immigrating or emigrants. They are just moving back and forth Bill On 19 Mar 2015 18:40, "J. P. Gilliver (John) via" <[email protected]> wrote: > > In message <[email protected]>, Bill > Webster via <[email protected]> writes: > >I have just created a custom event that I named Transit, for want of a > >better word. Any other suggestions for this name?

I use "resided" to track the migration of my ancestors. Maybe that would work for what you are trying to do. Jude On Thu, Mar 19, 2015 at 3:10 AM, Bill via <[email protected]> wrote: > But these people aren't either immigrating or emigrants. They are just > moving back and forth > Bill > ingOn 19 Mar 2015 18:40, "J. P. Gilliver (John) via" <[email protected]> > wrote: > > > > In message <[email protected]>, Bill > > Webster via <[email protected]> writes: > > >I have just created a custom event that I named Transit, for want of a > > >better word. Any other suggestions for this name? > > > > > >The advent of Shipping and other records makes this information > equivalent > > >to that in censuses. So, if Census is an included Event/Fact, maybe it > > >would be time to include whatever is decided to call what I have > > >(temporarily) named Transit. > > [] > > I use Emigrated/Immigrated (depending on whether it's a departure or > > arrival). Of course in these days of 'plane travel (and for ships when > > short journeys are involved), it can be the same day, so maybe your new > > event type _is_ needed. > > -- > > J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)[email protected]+H+Sh0!:`)DNAf > > > > "I'm a self-made man, thereby demonstrating once again the perils of > unskilled > > labor..." - Harlan Ellison > > 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 > > 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 >

In message <[email protected]>, Bill Webster via <[email protected]> writes: >I have just created a custom event that I named Transit, for want of a >better word. Any other suggestions for this name? > >The advent of Shipping and other records makes this information equivalent >to that in censuses. So, if Census is an included Event/Fact, maybe it >would be time to include whatever is decided to call what I have >(temporarily) named Transit. [] I use Emigrated/Immigrated (depending on whether it's a departure or arrival). Of course in these days of 'plane travel (and for ships when short journeys are involved), it can be the same day, so maybe your new event type _is_ needed. -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)[email protected]+H+Sh0!:`)DNAf "I'm a self-made man, thereby demonstrating once again the perils of unskilled labor..." - Harlan Ellison

I have just created a custom event that I named Transit, for want of a better word. Any other suggestions for this name? The advent of Shipping and other records makes this information equivalent to that in censuses. So, if Census is an included Event/Fact, maybe it would be time to include whatever is decided to call what I have (temporarily) named Transit. We don't have censuses for all countries. In my present case I am documenting a few families who were tea planters in Ceylon/Sri Lanka, but as they always declare if they turn up in a British census, they are British subjects. Only by their comings and goings by ships in and out of Ceylon have I been able to put together much of their information. Bill

Fortunately in my case having the wrong gender is an uncommon problem. I think the reason it has happened is because if one clicks anywhere near the gender boxes of an unmarried individual it will change the gender without question (bk6). So one just bumps along knowing that George is a male. George eventually marries Jane and they have children. Then I print a report saying that George is the mother and Mary is the father. I think that once the gender is set that it should not change without having to confirm the change. Jerry On Tuesday, March 17, 2015 10:31 PM, Paul J. Lareau via <[email protected]> wrote: A very common error (in my BK data) that is rather invisible until I encounter it later when adding marriages to people initially added as children, is that the already entered child, added long ago, was given the wrong gender accidentally.  This can happen due to "unisex" prenaming which is so common now, but the frequency of this error goes far beyond that situation.  A suggestion, John, although I have no idea if there is a coding way to implement it, is this. The current situation is that when entering a person or series of people for whom no automatic gender assignment is applied (it is automatically supplied, for example, in the case of entering a spouse or parent), and we might be typing fast, and not looking at the screen, when the window comes up to choose M, F, or U, and we either typed an ineligible character, typed the choice too lightly, or simply forgot to enter anything at all, the window remains there waiting for us to type on of the appropriate 3 characters, even though we have already starting to type the event line.  Progressing along the event line, it accepts the first M, F, or U you type, sets the gender to that code regardless of reality, enters what we have typed (including the letter it also used to indicate gender) and continues on typing the event content correctly.  The most common situation is for M & F, since the systems ignores the entry of any other keystrokes (including  numbers), often quietly makes entries masculine if the very next event date is in March or May, or feminine if the date is in February. While this does not prevent all errors of this kind, it would help if the NEXT keystroke that the system detects after the "set gender" window comes up, unless it was an M, F, or U, would not clear the window, and not proceed to gather additional data.  The best bet would be to force the entry to stop until the person clicks one of the check boxes that are showing (rather than a letter).    What has to be done is prevent the system from adding gender based on the presence of the appropriate letters in the text that follows. Better that doesn't allow you past the required gender code.  You would still be able to select the M, F, or U, rather than use the check box if that one of the codes were that VERY FIRST KEYSTROKE after the window came up. Paul J. Lareau 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

To Paul Lareau I will have the program beep if it is waiting for M F and you type some other letter first. That will solve some of your problem. However, if you type May or March it will see the M as Male. So if you see any dates of ay or arch then you will know to check to see if the person should be female instead of male. John Steed ----- Original Message ----- From: "Paul J. Lareau via" <[email protected]> To: <[email protected]> Sent: Tuesday, March 17, 2015 10:30 PM Subject: [BK] Initial Child Gender Assignment Typo >A very common error (in my BK data) that is rather invisible until I > encounter it later when adding marriages to people initially added as > children, is that the already entered child, added long ago, was given > the wrong gender accidentally. This can happen due to "unisex" > prenaming which is so common now, but the frequency of this error goes > far beyond that situation. A suggestion, John, although I have no idea > if there is a coding way to implement it, is this. > > The current situation is that when entering a person or series of people > for whom no automatic gender assignment is applied (it is automatically > supplied, for example, in the case of entering a spouse or parent), and > we might be typing fast, and not looking at the screen, when the window > comes up to choose M, F, or U, and we either typed an ineligible > character, typed the choice too lightly, or simply forgot to enter > anything at all, the window remains there waiting for us to type on of > the appropriate 3 characters, even though we have already starting to > type the event line. Progressing along the event line, it accepts the > first M, F, or U you type, sets the gender to that code regardless of > reality, enters what we have typed (including the letter it also used to > indicate gender) and continues on typing the event content correctly. > The most common situation is for M & F, since the systems ignores the > entry of any other keystrokes (including numbers), often quietly makes > entries masculine if the very next event date is in March or May, or > feminine if the date is in February. > > While this does not prevent all errors of this kind, it would help if > the NEXT keystroke that the system detects after the "set gender" window > comes up, unless it was an M, F, or U, would not clear the window, and > not proceed to gather additional data. The best bet would be to force > the entry to stop until the person clicks one of the check boxes that > are showing (rather than a letter). What has to be done is prevent > the system from adding gender based on the presence of the appropriate > letters in the text that follows. Better that doesn't allow you past the > required gender code. You would still be able to select the M, F, or U, > rather than use the check box if that one of the codes were that VERY > FIRST KEYSTROKE after the window came up. > > Paul J. Lareau > > > > > 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 >

A very common error (in my BK data) that is rather invisible until I encounter it later when adding marriages to people initially added as children, is that the already entered child, added long ago, was given the wrong gender accidentally. This can happen due to "unisex" prenaming which is so common now, but the frequency of this error goes far beyond that situation. A suggestion, John, although I have no idea if there is a coding way to implement it, is this. The current situation is that when entering a person or series of people for whom no automatic gender assignment is applied (it is automatically supplied, for example, in the case of entering a spouse or parent), and we might be typing fast, and not looking at the screen, when the window comes up to choose M, F, or U, and we either typed an ineligible character, typed the choice too lightly, or simply forgot to enter anything at all, the window remains there waiting for us to type on of the appropriate 3 characters, even though we have already starting to type the event line. Progressing along the event line, it accepts the first M, F, or U you type, sets the gender to that code regardless of reality, enters what we have typed (including the letter it also used to indicate gender) and continues on typing the event content correctly. The most common situation is for M & F, since the systems ignores the entry of any other keystrokes (including numbers), often quietly makes entries masculine if the very next event date is in March or May, or feminine if the date is in February. While this does not prevent all errors of this kind, it would help if the NEXT keystroke that the system detects after the "set gender" window comes up, unless it was an M, F, or U, would not clear the window, and not proceed to gather additional data. The best bet would be to force the entry to stop until the person clicks one of the check boxes that are showing (rather than a letter). What has to be done is prevent the system from adding gender based on the presence of the appropriate letters in the text that follows. Better that doesn't allow you past the required gender code. You would still be able to select the M, F, or U, rather than use the check box if that one of the codes were that VERY FIRST KEYSTROKE after the window came up. Paul J. Lareau

To Joe. HUSB means the husband in the family adopted the child. n ADOP [Y|<NULL>] {1:1} +1 <<EVENT_DETAIL>> {0:1} +1 FAMC @<XREF:FAM>@ {0:1} +2 ADOP <ADOPTED_BY_WHICH_PARENT> {0:1} ADOPTED_BY_WHICH_PARENT: = {Size=1:4} [ HUSB | WIFE | BOTH ] A code which shows which parent in the associated family record adopted this person. Where: HUSB =The HUSBand in the associated family adopted this person. WIFE =The WIFE in the associated family adopted this person. BOTH =Both HUSBand and WIFE adopted this person. ----- Original Message ----- From: "Joe via" <[email protected]> To: <[email protected]> Sent: Thursday, March 12, 2015 6:06 PM Subject: [BK] Adoptions in gedcom >I have a child entered as mother : natural and father : adoptive. The > gedcom file then list ADOP HUSB under the child and when imported by > other programs like Rootsweb a line under the child says Adopted Husband > which seems confusing since he died at age 6. Seems like the gedcom > should generate ADOP FATHER or is this another quirk in gedcom standards? > 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 >

I have a child entered as mother : natural and father : adoptive. The gedcom file then list ADOP HUSB under the child and when imported by other programs like Rootsweb a line under the child says Adopted Husband which seems confusing since he died at age 6. Seems like the gedcom should generate ADOP FATHER or is this another quirk in gedcom standards?

Hi, Running version 7.0.43 Registered I've run a Quality check against my BK database and get the following message. Reading marriage file Marriage number:808 the sex of this person appears to be incorrect based on marriage Husband: *REUSE* #3200 Unknown Wife: Change Husband to male and Wife to Female No changes I have opted for the 'No change' as I don't know what this is. How do I find out what marriage 808 is? I have tried to check on person 3200 but this is a deleted record. Any suggestions please. Anthony Williams

Hi John, When I replied to Jeff, I had not received John Steed's or Otto's replies and so was asking for clarification of the query. Confusion caused either by time zones, or Yahoo mail going funny, again. Regards Steve On 08/03/2015 09:48, J. P. Gilliver (John) via wrote: > In message <[email protected]>, Steve via <[email protected]> > writes: >> Hi Jeff, >> >> I've just run this on my tree and showed up 24 typos as in century of >> death before century of birth ( oops! ) but nothing relating to ages of >> siblings and I have siblings where there is a gap of over 10 years >> between them due to absence of father. >> >> So I'm not too sure what you mean. > [] > As John has explained, it's 6½ months, not years - and it's a minimum, > not a maximum (i. e. siblings born closer together than that _probably_ > indicate an error - though it can happen, in which case it can be > excluded from future checks). > > 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 > . >

Hi Carole, The usual way to change your email address on a RootsWeb mailing list is to unsubscribe the old one and then to re-subscribe with the new one, or even the other way round ;-) Regards Steve On 08/03/2015 13:19, Carole Durch via wrote: > Please update my email address to: [email protected] > > > Carole Durch > > Office: (316) 210-5710 > > Email: [email protected] > 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 > . >

Steve I have that problem sometimes and they are in my bulk or spam folder on Yahoo. Check there. Jim -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Steve via Sent: Sunday, March 08, 2015 12:13 PM To: [email protected] Subject: Re: [BK] Reasonableness check Hi John, When I replied to Jeff, I had not received John Steed's or Otto's replies and so was asking for clarification of the query. Confusion caused either by time zones, or Yahoo mail going funny, again. Regards Steve On 08/03/2015 09:48, J. P. Gilliver (John) via wrote: > In message <[email protected]>, Steve via <[email protected]> > writes: >> Hi Jeff, >> >> I've just run this on my tree and showed up 24 typos as in century of >> death before century of birth ( oops! ) but nothing relating to ages >> of siblings and I have siblings where there is a gap of over 10 years >> between them due to absence of father. >> >> So I'm not too sure what you mean. > [] > As John has explained, it's 6½ months, not years - and it's a minimum, > not a maximum (i. e. siblings born closer together than that > _probably_ indicate an error - though it can happen, in which case it > can be excluded from future checks). > > 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 . > 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

In message <[email protected]>, Steve via <[email protected]> writes: >Hi Jeff, > >I've just run this on my tree and showed up 24 typos as in century of >death before century of birth ( oops! ) but nothing relating to ages of >siblings and I have siblings where there is a gap of over 10 years >between them due to absence of father. > >So I'm not too sure what you mean. [] As John has explained, it's 6½ months, not years - and it's a minimum, not a maximum (i. e. siblings born closer together than that _probably_ indicate an error - though it can happen, in which case it can be excluded from future checks).

Please update my email address to: [email protected] Carole Durch Office: (316) 210-5710 Email: [email protected]

On Sat, 7 Mar 2015 14:43:43 -0600, jstockham via <[email protected]> wrote: >From: jstockham [mailto:[email protected]] >Sent: Wednesday, March 04, 2015 3:46 PM >To: John Steed and others >Subject: Children's list which had been deleted shows up on report > >We had the wives of an ancestor mixed up. The second wife was shown as the >mother of the first 9 children but it was found that she was not - they were >born of another woman. > >I put the children all under the first wife and then deleted the list as >shown under the second wife, leaving her with only 2 children who had not >been mentioned in the husband's will. > >It all looked ok, but then I went to print a family group sheet and found >that the first 9 children were listed with their mother correctly but then >the second wife is shown with her two followed by a double line and then all >the first 9 children! They do not show on her page, why would they show on >the group sheet and what do I do to get them off of it? > First of all you should ALWAYS tell what version you are using 7.0.44 If it is /, have your re-indexed the database -- Otto Jørgensen http://home.online.no/~otjoerge/ All email is checked by NIS2014

To Jean in OK If you have BK 6.6 then you do not need to "re-index the database" Go to Edit and show the man with the two wives. Click the down arrow to the right of the spouse names. Do you see a spouse called "not entered"? If yes, pick that spouse. Then when "not entered" shows as the spouse, click from the top menu Delete, LINK to SPOUSE. John Steed ----- Original Message ----- From: "jstockham via" <[email protected]> To: <[email protected]> Sent: Saturday, March 07, 2015 3:43 PM Subject: [BK] FW: Children's list which had been deleted shows up on report > > > > > From: jstockham [mailto:[email protected]] > Sent: Wednesday, March 04, 2015 3:46 PM > To: John Steed and others > Subject: Children's list which had been deleted shows up on report > > > > We had the wives of an ancestor mixed up. The second wife was shown as > the > mother of the first 9 children but it was found that she was not - they > were > born of another woman. > > I put the children all under the first wife and then deleted the list as > shown under the second wife, leaving her with only 2 children who had not > been mentioned in the husband's will. > > > > It all looked ok, but then I went to print a family group sheet and found > that the first 9 children were listed with their mother correctly but then > the second wife is shown with her two followed by a double line and then > all > the first 9 children! They do not show on her page, why would they show > on > the group sheet and what do I do to get them off of it? > > > > Jean in OK > > 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 >

Hi Jeff, I've just run this on my tree and showed up 24 typos as in century of death before century of birth ( oops! ) but nothing relating to ages of siblings and I have siblings where there is a gap of over 10 years between them due to absence of father. So I'm not too sure what you mean. Regards Steve On 07/03/2015 13:12, Jeff Stewart via wrote: > Why was 6.5 years age difference between siblings used? I just found this > feature and had to make many corrections to my family tree. > 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 > . >

On Sat, 7 Mar 2015 10:12:09 -0500, Léandre Maillet via <[email protected]> wrote: >Hi, > >I’m curious as to a way to back-up large data file with several photos, marriage and death certificats, etc. > >I have over 600 000 persons with 40 000 .jpegs. >It would take app. 4 days to run a backup (baring any computer or other cliches). > >Is there a way to back-up smaller data files and gradually building it up to the whole set? >For example, to run a backup with 20-30000 persons, then adding another 2000, etc. Take a copy of your datafolder ( DATA) with the tree subfolders to an external Hardisk The new routine of Backup in BK7 has also facilities to remeber what is backuped earlier som it will not take so longtime next time. -- Otto Jørgensen http://home.online.no/~otjoerge/ All email is checked by NIS2014

I have 6.6 and what does reindex the data base mean? JS -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Otto Jørgensen via Sent: Saturday, March 07, 2015 3:07 PM To: [email protected] Subject: Re: [BK] FW: Children's list which had been deleted shows up on report On Sat, 7 Mar 2015 14:43:43 -0600, jstockham via <[email protected]> wrote: >From: jstockham [mailto:[email protected]] >Sent: Wednesday, March 04, 2015 3:46 PM >To: John Steed and others >Subject: Children's list which had been deleted shows up on report > >We had the wives of an ancestor mixed up. The second wife was shown as >the mother of the first 9 children but it was found that she was not - >they were born of another woman. > >I put the children all under the first wife and then deleted the list >as shown under the second wife, leaving her with only 2 children who >had not been mentioned in the husband's will. > >It all looked ok, but then I went to print a family group sheet and >found that the first 9 children were listed with their mother correctly >but then the second wife is shown with her two followed by a double >line and then all the first 9 children! They do not show on her page, >why would they show on the group sheet and what do I do to get them off of it? > First of all you should ALWAYS tell what version you are using 7.0.44 If it is /, have your re-indexed the database -- Otto Jørgensen http://home.online.no/~otjoerge/ All email is checked by NIS2014 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