Looking through my list of locations, I spotted "Collier". It was obvious what had happened - I'd entered someone's occupation, but as event type as something other than Occupation which made whatever was in that column count as a location. However, _finding_ it wasn't easy. Since it was the result of a mistake, I couldn't search for a specific field, so had to use the Any field search; but since a lot of my ancestry is from mining areas, lots of them have "Colliery" - which includes Collier - in lots of places. I eventually found it, but I think it took me more than an hour (of looking through the individuals thrown up by the above search). [It had been entered as Ordination - I obviously hadn't pressed O twice.] Any suggestions on how I could have speeded the process of finding the error? (Changing the event type also would have lost the source; see separate thread.) -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf A. Top-posters. Q. What's the most irritating thing on Usenet?
John I just had the same situation, but I produced the "Locations with Events" report. I was 2,800 pages long. Luckily I printed it as a PDF file and was able to use Acrobat to search to the specific item. Jim -----Original Message----- From: J. P. Gilliver (John) [mailto:G6JPG-255@255soft.uk] Sent: Tuesday, January 15, 2019 6:51 AM To: bk@rootsweb.com Subject: [BK] an interesting task: finding a part-word Looking through my list of locations, I spotted "Collier". It was obvious what had happened - I'd entered someone's occupation, but as event type as something other than Occupation which made whatever was in that column count as a location. However, _finding_ it wasn't easy. Since it was the result of a mistake, I couldn't search for a specific field, so had to use the Any field search; but since a lot of my ancestry is from mining areas, lots of them have "Colliery" - which includes Collier - in lots of places. I eventually found it, but I think it took me more than an hour (of looking through the individuals thrown up by the above search). [It had been entered as Ordination - I obviously hadn't pressed O twice.] Any suggestions on how I could have speeded the process of finding the error? (Changing the event type also would have lost the source; see separate thread.) -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf A. Top-posters. Q. What's the most irritating thing on Usenet? _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
To Jim Dell I guess you did not pick the option to search for only one location name. That is on the "Other Options" tab. Or else, perhaps you had a bad location that was just a couple letters long, like TH In that case finding all locations with TH would give you a lot. Here is a hint for cases like that: If you ever get a strange case of a location that is only 1 or 2 letters long, and you are trying to find who has that location, then before you use the Locations with Events routine to find it, go first to "File, Locations, Change Location Globally." Then type the bad location name and put that on the top line. So if the location is just two letters TH then put that on the top line. Then on the bottom line, change it to something that no other location has, like XYZ Then the routine will change the one bad location with common letters to a new name with uncommon letters. After that is done, you can use the Locations with Events and search for only location XYZ and it should find it easily. John Steed ________________________________ From: Jim Dell2 via BK <bk@rootsweb.com> Sent: Tuesday, January 15, 2019 12:50 PM To: bk@rootsweb.com Cc: Jim Dell2 Subject: [BK] Re: an interesting task: finding a part-word John I just had the same situation, but I produced the "Locations with Events" report. I was 2,800 pages long. Luckily I printed it as a PDF file and was able to use Acrobat to search to the specific item. Jim -----Original Message----- From: J. P. Gilliver (John) [mailto:G6JPG-255@255soft.uk] Sent: Tuesday, January 15, 2019 6:51 AM To: bk@rootsweb.com Subject: [BK] an interesting task: finding a part-word Looking through my list of locations, I spotted "Collier". It was obvious what had happened - I'd entered someone's occupation, but as event type as something other than Occupation which made whatever was in that column count as a location. However, _finding_ it wasn't easy. Since it was the result of a mistake, I couldn't search for a specific field, so had to use the Any field search; but since a lot of my ancestry is from mining areas, lots of them have "Colliery" - which includes Collier - in lots of places. I eventually found it, but I think it took me more than an hour (of looking through the individuals thrown up by the above search). [It had been entered as Ordination - I obviously hadn't pressed O twice.] Any suggestions on how I could have speeded the process of finding the error? (Changing the event type also would have lost the source; see separate thread.) -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf A. Top-posters. Q. What's the most irritating thing on Usenet? _______________________________________________ Remember - Use the Archives at https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiver.rootsweb.com%2Fcgi-bin%2Fsearch&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=jd3o4JHTxtyU7t%2F2Nueb%2F7r4vXw1IPMZCeVMKoEoT%2Bo%3D&reserved=0 _______________________________________________ Email preferences: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=1Sjh9j9Uq8brHiOjmHGweb3dwBfAZnaKxDZstJfuw%2Fo%3D&reserved=0 Unsubscribe https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Fbk%40rootsweb.com&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=5u9FU%2Boo7a4nNfiKizJgkjW%2BbIbs%2F3ECeG6AaDyJarM%3D&reserved=0 Privacy Statement: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=wexreFzZqoee27Gi0TpHUbv1UyyiBA3oTyovU51NGHA%3D&reserved=0 Terms and Conditions: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=BVgN2kDIek2xLYiQ2GLYVdjkipIiOwqjstoJdJU1Y58%3D&reserved=0 Rootsweb Blog: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=uoygDuoNdWhLdYh2Temw%2FzcxnkhcMdiDM2ai7N5f9Ec%3D&reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiver.rootsweb.com%2Fcgi-bin%2Fsearch&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=jd3o4JHTxtyU7t%2F2Nueb%2F7r4vXw1IPMZCeVMKoEoT%2Bo%3D&reserved=0 _______________________________________________ Email preferences: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=1Sjh9j9Uq8brHiOjmHGweb3dwBfAZnaKxDZstJfuw%2Fo%3D&reserved=0 Unsubscribe https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Fbk%40rootsweb.com&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=5u9FU%2Boo7a4nNfiKizJgkjW%2BbIbs%2F3ECeG6AaDyJarM%3D&reserved=0 Privacy Statement: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=wexreFzZqoee27Gi0TpHUbv1UyyiBA3oTyovU51NGHA%3D&reserved=0 Terms and Conditions: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=BVgN2kDIek2xLYiQ2GLYVdjkipIiOwqjstoJdJU1Y58%3D&reserved=0 Rootsweb Blog: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&data=02%7C01%7C%7C7a15cb76c23c45e41f8b08d67ae82ccc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831534927389060&sdata=uoygDuoNdWhLdYh2Temw%2FzcxnkhcMdiDM2ai7N5f9Ec%3D&reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
In message <BN7PR02MB509265FC8FA9B71FF13A8D9F91810@BN7PR02MB5092.namprd02.prod.outlo ok.com>, John Steed <brothers_keeper@msn.com> writes: >To Jim Dell > >I guess you did not pick the option to search for only one location >name. That is on the "Other Options" tab. > >Or else, perhaps you had a bad location that was just a couple letters >long, like TH > >In that case finding all locations with TH would give you a lot. I tended to have a lot of those, from when I'd entered part of a location then went to press F8, but hit F7 by mistake instead. (I now _immediately_ correct the error, then use the "delete unused locations" utility.) > >Here is a hint for cases like that: >If you ever get a strange case of a location that is only 1 or 2 >letters long, and you are trying to find who has that location, then >before you use the Locations with Events routine to find it, go first >to "File, Locations, Change Location Globally." Then type the bad >location name and put that on the top line. So if the location is just >two letters TH then put that on the top line. Then on the bottom line, >change it to something that no other location has, like XYZ > >Then the routine will change the one bad location with common letters >to a new name with uncommon letters. > >After that is done, you can use the Locations with Events and search >for only location XYZ and it should find it easily. Excellent trick! [] -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf After I'm dead I'd rather have people ask why I have no monument than why I have one. -Cato the Elder, statesman, soldier, and writer (234-149 BCE)
When searching for a word and you don’t want to include words that include your search word: type the word then type a space then hit enter. By putting the space after the word it forces the computer to exclude longer words that include the word you are looking for. For example type “ under “ and it won’t return underwater, understand, etc. Hope this helps in future searches Regards Karlena Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 ________________________________ From: Jim Dell2 via BK <bk@rootsweb.com> Sent: Tuesday, January 15, 2019 11:50:43 PM To: bk@rootsweb.com Cc: Jim Dell2 Subject: [BK] Re: an interesting task: finding a part-word John I just had the same situation, but I produced the "Locations with Events" report. I was 2,800 pages long. Luckily I printed it as a PDF file and was able to use Acrobat to search to the specific item. Jim -----Original Message----- From: J. P. Gilliver (John) [mailto:G6JPG-255@255soft.uk] Sent: Tuesday, January 15, 2019 6:51 AM To: bk@rootsweb.com Subject: [BK] an interesting task: finding a part-word Looking through my list of locations, I spotted "Collier". It was obvious what had happened - I'd entered someone's occupation, but as event type as something other than Occupation which made whatever was in that column count as a location. However, _finding_ it wasn't easy. Since it was the result of a mistake, I couldn't search for a specific field, so had to use the Any field search; but since a lot of my ancestry is from mining areas, lots of them have "Colliery" - which includes Collier - in lots of places. I eventually found it, but I think it took me more than an hour (of looking through the individuals thrown up by the above search). [It had been entered as Ordination - I obviously hadn't pressed O twice.] Any suggestions on how I could have speeded the process of finding the error? (Changing the event type also would have lost the source; see separate thread.) -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf A. Top-posters. Q. What's the most irritating thing on Usenet? _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
To J P Gilliver If there is a strange location name, and you want to find what event has that location, then go to Lists, "Locations with Events". Then set the option for "Show all events" Then on the "Other Options" tab pick "Show only locations containing:" and type the location such as: Collier Then click Preview. It should show which event has that location name. John Steed ________________________________ From: J. P. Gilliver (John) <G6JPG-255@255soft.uk> Sent: Tuesday, January 15, 2019 11:51 AM To: bk@rootsweb.com Subject: [BK] an interesting task: finding a part-word Looking through my list of locations, I spotted "Collier". It was obvious what had happened - I'd entered someone's occupation, but as event type as something other than Occupation which made whatever was in that column count as a location. However, _finding_ it wasn't easy. Since it was the result of a mistake, I couldn't search for a specific field, so had to use the Any field search; but since a lot of my ancestry is from mining areas, lots of them have "Colliery" - which includes Collier - in lots of places. I eventually found it, but I think it took me more than an hour (of looking through the individuals thrown up by the above search). [It had been entered as Ordination - I obviously hadn't pressed O twice.] Any suggestions on how I could have speeded the process of finding the error? (Changing the event type also would have lost the source; see separate thread.) -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf A. Top-posters. Q. What's the most irritating thing on Usenet? _______________________________________________ Remember - Use the Archives at https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiver.rootsweb.com%2Fcgi-bin%2Fsearch&data=02%7C01%7C%7C74c78ae9a2514f9a1aff08d67adfe1e1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831499310653013&sdata=kDr817zCXIDh9YZQWKW%2B1UL0Pf%2BFJKnNA%2Fut%2B4jVZpY%3D&reserved=0 _______________________________________________ Email preferences: https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&data=02%7C01%7C%7C74c78ae9a2514f9a1aff08d67adfe1e1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831499310653013&sdata=MLJM%2B30vb%2FQusCEladu%2BO%2FZdps26FZIEgx9WVAlaLhQ%3D&reserved=0 Unsubscribe https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Fbk%40rootsweb.com&data=02%7C01%7C%7C74c78ae9a2514f9a1aff08d67adfe1e1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831499310653013&sdata=w7QjQlVfMuBOrummus8xjMWI%2B%2FsMpl8g0SB1ajcF2K4%3D&reserved=0 Privacy Statement: https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&data=02%7C01%7C%7C74c78ae9a2514f9a1aff08d67adfe1e1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831499310653013&sdata=xOCVh4kgpzPzE2WbypiDwD0DXkMiRo4Ij5esffQ27%2FE%3D&reserved=0 Terms and Conditions: https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&data=02%7C01%7C%7C74c78ae9a2514f9a1aff08d67adfe1e1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831499310653013&sdata=4HFy7p%2Bf6P0dNNJbw0Zhldqg7NAvzr2Ejo%2FxOwhgPEU%3D&reserved=0 Rootsweb Blog: https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&data=02%7C01%7C%7C74c78ae9a2514f9a1aff08d67adfe1e1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831499310653013&sdata=CIsT5ROx5LUha9xTjhyOgk%2BC6W2He%2BkN4CPGyp22pRY%3D&reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
In message <BN7PR02MB5092146FD8395E5CF2C448D891810@BN7PR02MB5092.namprd02.prod.outlo ok.com>, John Steed <brothers_keeper@msn.com> writes: >To J P Gilliver > >If there is a strange location name, and you want to find what event >has that location, then go to Lists, "Locations with Events". > >Then set the option for "Show all events" > >Then on the "Other Options" tab pick "Show only locations containing:" >and type the location such as: Collier > >Then click Preview. > >It should show which event has that location name. [] Thanks! I wasn't aware of that option. It'd still pick up all the occurrences of "Colliery", but at least it'd limit it to where that occurs in locations (i. e. not in comments etc.). Now, if only I could alt-tab (or similar) from such a "Preview" to the edit screen ... (-: -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf The early worm gets the bird.
John Gilliver To use the <Alt>-<Tab> with your "coal miners" ...I looked it up :-) ... print your "location" list to a pdf file and then bring up the pdf file along with BK. Also if you think you might need to track your progress through the pdf file there is a tool in the Adobe Acrobat Reader. Choose the "Fill and Sign" tool. You can put a check mark or X when you've completed fixing a location item in BK. Then you can re-save the pdf file with those marks. (Don't "sign" it or no more changes). Regards to all Roy Marriott On Tue, Jan 15, 2019 at 10:02 AM J. P. Gilliver (John) <G6JPG-255@255soft.uk> wrote: > > In message > <BN7PR02MB5092146FD8395E5CF2C448D891810@BN7PR02MB5092.namprd02.prod.outlo > ok.com>, John Steed <brothers_keeper@msn.com> writes: > >To J P Gilliver > > > >If there is a strange location name, and you want to find what event > >has that location, then go to Lists, "Locations with Events". > > > >Then set the option for "Show all events" > > > >Then on the "Other Options" tab pick "Show only locations containing:" > >and type the location such as: Collier > > > >Then click Preview. > > > >It should show which event has that location name. > [] > Thanks! I wasn't aware of that option. It'd still pick up all the > occurrences of "Colliery", but at least it'd limit it to where that > occurs in locations (i. e. not in comments etc.). > > Now, if only I could alt-tab (or similar) from such a "Preview" to the > edit screen ... (-: > -- > J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf > > The early worm gets the bird. > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
In message <CAK+BQvwa2+MsPtJvsuDgCC8OEw43BF6rQHFOCW23C=7OZ4NiWQ@mail.gmail.com>, Roy Marriott <roy.marriott@gmail.com> writes: >John Gilliver >To use the <Alt>-<Tab> with your "coal miners" ...I looked it up :-) ... >print your "location" list to a pdf file and then bring up the pdf >file along with BK. Also if you think you might need to track your >progress through the pdf file there is a tool in the Adobe Acrobat >Reader. Choose the "Fill and Sign" tool. You can put a check mark or X >when you've completed fixing a location item in BK. Then you can >re-save the pdf file with those marks. (Don't "sign" it or no more >changes). >Regards to all >Roy Marriott [] Thanks. I'd been hoping to avoid the print-to-PDF trick. The suggestion that somebody has made of using "Locations with events" - which _does_ have a preview button - would have worked, though. (OK, specifying "collier" _would_ still have also hit all the locations that have "Colliery", but would have listed the "collier" events separately under their own heading.) -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf After I'm dead I'd rather have people ask why I have no monument than why I have one. -Cato the Elder, statesman, soldier, and writer (234-149 BCE)