On Sun, 27 May 2012 07:29:20 -0400, "Carole Edwards Caruso" <carolec@stny.rr.com> wrote: >Thanks for all the thoughts on the this matter. And thank you, John, for explaining the difficulty of changing the number of characters allowed. > >We each have our own needs and ways of doing our genealogy. When I need more room, I will add the event twice so it will appear: > >Buried: 12 Nov 1800 at Stainland, Yorkshire, England >Buried: in Providence United Reformed Church Cemetery, Beestonley Lane, Section 3 , Lot 387 Bt us the last barn of the grave identification is a part of the source and are among the same for many The spcific location on the gravyard is a source part, but the gravyard and its location is Common for many grave. http://haugesund.kirken.no/doc/index.html gravesyard in Haugsund where my parents, grandparens are burried -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON
On Sun, 27 May 2012 07:41:05 -0400, "Jim Ramaley" <jramaley@comcast.net> wrote: >Otto, > >Please read my note more carefully before you fire off your typically negative comment. > >Your "subject for subject" comment after your "etc" in item 7 is strange. I had TWO suggestions. You have 7, well actually only 6, sections -- none of which address my main point that the source citation fields be used for further detail if desired. > >1. You are in agreement with me that one should use abbreviations IF they are not confusing. What point are you trying to make that is different from mine? In my case of 8600 locations I had only 1 what was even close to the maximum -- and I have now reviewed it and changed it to be more readable -- and shorter! > >2. Why should BK substitute for a history book? There are examples even here in Pennsylvania of some locations having been in as many as 6 counties at different times in history. Should I list all six in the location field? If in compiling a genealogy you want to include a chapter on history or on geography you can easily do so and it will be more complete and more readable than trying to fit it into a 100-character (or even 200-character!) location field. > >3. My point exactly. So what is the point of your comment? > >4. See number 2. Why keep beating a dead horse. > >5. I have over 8000 locations. There are only a few that someone would have trouble locating. Why set up GPS for every location? If GPS is important for a specific location, use a source citation field and put it in. Are you going to search on GPS so that it needs to be a separately indexed field? > >6. Your BK must work differently than mine. I can put in a partial location and F8 supplies candidates just like *. Without the *. > >Nowhere do I say that John should stop development. I said that I am against structural changes if there are good alternatives. I have often found that thoughtful users can themselves suggest work arounds and I have seen many suggestions from readers of this forum that do just that > >My opinion on avoiding structural changes is based upon a career in programming and systems design, and the managing of teams of such people. I stand by it. There are times when a structural change is required, but it is a tool of last resort, not of first resort. You can do it just in the way yhou want. No problem Allready to day there is an option to shorten name doe om chart and report We want an option to shorten names in reports. And we hope John will do it We will use in Personally I have about 30000 persons in my database and about 7000 different location and about 1000 mastersourses and ditto 1000 masterSources. We want good reports and the number mention above is of no minor interes for my grandparents and relatives. They are interested that my Granduncle is burried i Alaska, but not so mucg on what exact grav. Hoever that information is taken well care of in my data and I can easerly print reports with all details both for location and lkines in a specific chuchbooks or census, but mostly that are for recerch work, not for common family reading. It is possible that we in scandinavian have done the work in BK different than yours, but we are a great number of scandinavian doing the same and that is also according to our tradition way of handling sources and information. Mostly all our sources are free of use and mostly all links are permently and by that that is used a lot and the way of using sources is common by all of us. May be myou shoukld install the Norwegian or Danish version and use that for you data and try the <f1> and if not understanding, The Google translate will help you BK does not substitute a history book, but history around farms etc, also gives a lot information why so many Norwgian did Emigrate to USA, Cana, Australia, Hawai etc That is very important for a family book and understanding of the life of all my relatives. The general historybooks does not tell about the poor situation on small farms with 10-16 children and wifes that did die in bith or male died at sea and lett behind widows on a small farm with 10 children. That is an importan jhistory of a family. At leas that is important information for most Norwegian in this hobby. -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON
Since I have not read all of the replies to your question, perhaps I should just let well enough alone - but here is my two cents worth: I avoid this problem by putting the City, County, State in Location/Description and the name of the burial place, etc. in the "N" section. Works well for me. BJK > You could change the second buried to interred. Looks nice > > > * smiles to you* > Patricia > > From: Carole Edwards Caruso > Sent: Sunday, May 27, 2012 6:29 AM > To: bk@rootsweb.com > Subject: Re: [BK] Number of Characters Allowed > > Thanks for all the thoughts on the this matter. And thank you, John, for > explaining the difficulty of changing the number of characters allowed. > > We each have our own needs and ways of doing our genealogy. When I need > more room, I will add the event twice so it will appear: > > Buried: 12 Nov 1800 at Stainland, Yorkshire, England > Buried: in Providence United Reformed Church > Cemetery, Beestonley Lane, Section 3 , Lot 387 > > > Does anyone see any problem with this? > > Carole > 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 > 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 >
Hello Jim! On Sunday, May 27, 2012 you wrote in [BK]: JR> Nowhere do I say that John should stop development... John looks over the horizon and is open to new minds. My previous experience is, that he tries to install features, which gave a compatibility to other Genealogy solutions. The expansion of the fields of places to 150 characters is just one example. -- bye, Otmar Mayr
Carol: I know you can do what you say and it shows properly on the edit screen. Are you sure it will print that way say on a group sheet, I seem to remember that it printed only one instance of say buried. Give a try and see if its OK. Dave Bradshaw -----Original Message----- From: bk-bounces@rootsweb.com [mailto:bk-bounces@rootsweb.com] On Behalf Of Carole Edwards Caruso Sent: May 27, 2012 7:29 AM To: bk@rootsweb.com Subject: Re: [BK] Number of Characters Allowed Thanks for all the thoughts on the this matter. And thank you, John, for explaining the difficulty of changing the number of characters allowed. We each have our own needs and ways of doing our genealogy. When I need more room, I will add the event twice so it will appear: Buried: 12 Nov 1800 at Stainland, Yorkshire, England Buried: in Providence United Reformed Church Cemetery, Beestonley Lane, Section 3 , Lot 387 Does anyone see any problem with this? Carole 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
Patricia - Beautiful! Thank you! And this sure solves my problem! Carole Subject: Re: [BK] Number of Characters Allowed To: <bk@rootsweb.com> Message-ID: <FA1E55B928144481AF265463EE49BDB0@PatriciaPC> Content-Type: text/plain; charset="iso-8859-1" You could change the second buried to interred. Looks nice * smiles to you* Patricia
Dave, thank you for mentioning this. It threw me into a short-lived panic as I have used the BURIAL event more than when a person was first buried in cemetery #1 and their remains later moved to cemetery #2. I just now checked the group sheet and register reports (2 reports I use most) and both BURIAL events show in the order listed on the EDIT screen. In the case I tested I had a date for the first burial but not have one for the second. I had them listed on the EDIT screen in cemetery #1, cemetery #2 order. Is there a better way to record when a body is moved from one cemetery to another? ----- From: Dave Bradshaw <davebradshaw@sympatico.ca> Subject: Re: [BK] Number of Characters Allowed Date: Sun, 27 May 2012 14:03:11 -0400 References: <579021D4621D4957A2FF7C6B8CC13957@Blackie> In-Reply-To: <579021D4621D4957A2FF7C6B8CC13957@Blackie> Carol: I know you can do what you say and it shows properly on the edit screen. Are you sure it will print that way say on a group sheet, I seem to remember that it printed only one instance of say buried. Give a try and see if its OK. Dave Bradshaw ----
On Fri, 25 May 2012 23:16:11 -0400, "Jim Ramaley" <jramaley@comcast.net> wrote: >John, > >I am not in favor of structural changes to a program to accommodate a perceived need when that need can be easily handled with a work-around. > >The issue seems to be that folks want to use the Location field in ways that were not intended. > >For example, some want it to be a history lesson by including former names of a location. I recall seeing one some years ago who wanted to include the fact that many current-day European locations were, historically, part of the Holy Roman Empire. > >Some want the location to be GPS exact and while that might be technically possible today, it is not nearly as useful as saying something like "Schlosser's Church, Unionville/Neff, North Whitehall Twp, Lehigh Co, PA . > >I use the location field to help a reader or fellow researcher in understanding enough of the location of a given event to visit or to do further research. When I go into the field I find that your report "Locations with Events" to be of great value. But if locations were so specific that they are unique to a given individual, this report would be much less useful. > >There are at least two ways that greater precision can be given in specifying the location for an event. > >1. Events have a source field. The source screen has several fields > that could be populated to make the citation more geographically > precise. For example, if one wants to specify the section, lot, > and plot number for a grave, there are comment fields, text > fields, and page / reel number fields [that's what I use]. These > print out on reports and you would want to cite a source anyway. > >2. If a location has "changed" because of political activity (example: > a new county is formed out of an old one) it usually takes only a > few characters out of the 100 available to so indicate. For > example, I have ancestors buried in what is now Lehigh County, PA, > but at the time of the probate of the wills the county was > Northampton. If necessary for understanding, I use "Heidelberg > Twp, Lehigh (formerly Northampton) Co, PA" > >I have read that some folks don't want to use abbreviations because they can be confusing. I have found that to be the case only where the political subdivision is not known to the researcher and has been left blank. For example, here in Adams County, PA the westernmost township is Franklin Twp. The next county to our west is also named Franklin. So, giving a citation to "Franklin" but omitting the political subdivision is certainly confusing if citing an event in this area. > >Bottom line: I have 8666 locations in my database. Average length is 27 with a standard deviation of 9. Largest location has 98 characters with only 10 having a length of 70 or more (and those 10 could have been shortened by abbreviations if I saw the value is so doing. > I don't agree mostly. I firstly say that fields are used for what they are specified!! 1. If I have a very long name as specified in a previous answer I see the Idea to shorten that for the reader, but I agree that it is also necessary to give the complete name of location. The example was 108 characters and for me I think that is to long in a book. If you repeat that name of location several time, for all events on the same page (born, birth, marry, death, education etc) My idea was to use a short abr. in the text and have a common footnotes down on the same page telling the complete name. Paper used has normal limit of 112 characters on a line. 2. Names is necessary to also give the political history. Many Norwegian have roots from Sweden and some of the location that now is Swedish was earlier Norwegian. This is normal and similar in many countries http://en.wikipedia.org/wiki/J%C3%A4mtland The sources here is to be found in both Norway and Sweden and have to be specified and it is a need for the reader to understand that. So there is a need to have soma information. W can put that in the detail of Location. It is waist of time and paper to tell this several places in a biography of the family BK has not yet any good way to connect places, nor when they have new administration or changed name Sankt Petersburg = Petrograd = Leningrad For names on person we have a lot of Alternatives names. That seems to be OK, but not for location. For Persons and events we use biography and Notes, but not for Location (here we shall put that information into the biography under Edit or as Note)? To add storry of farms we normaly use http://www.dokpro.uio.no/rygh_ng/rygh_form.html http://www.dokpro.uio.no/perl/navnegransking/rygh_ng/rygh_visetekst.prl?s=e&Vise=Show&KRYSS128347@29149=on and that is sources for our farms with different way of naming/spelling farm-names 3. Many do want to include the history of a farm, a church etc to the history of a family. In stead of repeating this all the time for many persons in the family book you can add that once place and use that in the same way you make index 4. A location can beside change country as a result if was WWII also have different administration whether it is Civil or religion. The borders for the administration are different even in the same countries. 5. GPS is great and we can add coordinates to BK, even if the program not yet have the map connection. But we must also thing forward and not stop thinking of new ideas. 6. Search methods For name we can use * and ? to find the name directly. It is not perfect, but we have only F8 for location. On both we should be able to use the function "including" 7. Etc So I can continue with subject for subject. It is good future to have the possibility in the program, but that does not mean that everybody do have to use them all. And that is up to you to enter information into the program and it is up to you to use the possibilities. We can not tell users to not use the modern technique. We must hope that John can add it and give us the option to use the program, also in the future. It is also important that there will come new users, younger than we oldies will take the program forward to new generation. To stop developing the program is a bad idea -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON
Dick, It's probably a multi-step process, start with your common ancestors and make sure the children of each ancestor is in both files after that move another generation down (younger) and do the same. If you don't notice that one had a child or was married you miss a whole group of people. Go back and compare again after you enter the missing children and watch the children tab for the asterisk noting they have children, also watch the spouse name on both sides. Jim -----Original Message----- From: bk-bounces@rootsweb.com [mailto:bk-bounces@rootsweb.com] On Behalf Of Dick Rose Sent: Sunday, May 27, 2012 10:40 AM To: [BK] Subscribers Subject: [BK] Compare Routine I am currently working with my original database on the left and a database which was the result of a gedcom from one of my common DNA relatives on the right. The right side has numerous new people which I need to move to the left. The compare routine doesn't find these people. I am seeking the best way to identify the candidates to acquire into my original database. If there is something I am missing please advise how. The only way I have figured out is to run the routine with the new database on the left, but that doesn't provide for a way to move the people, only provides for identifying the ones that I have to go back to with the databases back in the original position. Got to be an easier way to compare right to left. Dick Rose dtrose@cox.net 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
On 5/25/2012 11:16 PM Jim Ramaley submitted the following: > John, > > I am not in favor of structural changes to a program to accommodate a perceived need when that need can be easily handled with a work-around. > > The issue seems to be that folks want to use the Location field in ways that were not intended. > > For example, some want it to be a history lesson by including former names of a location. I recall seeing one some years ago who wanted to include the fact that many current-day European locations were, historically, part of the Holy Roman Empire. > > Some want the location to be GPS exact and while that might be technically possible today, it is not nearly as useful as saying something like "Schlosser's Church, Unionville/Neff, North Whitehall Twp, Lehigh Co, PA . > > I use the location field to help a reader or fellow researcher in understanding enough of the location of a given event to visit or to do further research. When I go into the field I find that your report "Locations with Events" to be of great value. But if locations were so specific that they are unique to a given individual, this report would be much less useful. > > There are at least two ways that greater precision can be given in specifying the location for an event. > > 1. Events have a source field. The source screen has several fields that could be populated to make the citation more geographically precise. For example, if one wants to specify the section, lot, and plot number for a grave, there are comment fields, text fields, and page / reel number fields [that's what I use]. These print out on reports and you would want to cite a source anyway. > > 2. If a location has "changed" because of political activity (example: a new county is formed out of an old one) it usually takes only a few characters out of the 100 available to so indicate. For example, I have ancestors buried in what is now Lehigh County, PA, but at the time of the probate of the wills the county was Northampton. If necessary for understanding, I use "Heidelberg Twp, Lehigh (formerly Northampton) Co, PA" > > I have read that some folks don't want to use abbreviations because they can be confusing. I have found that to be the case only where the political subdivision is not known to the researcher and has been left blank. For example, here in Adams County, PA the westernmost township is Franklin Twp. The next county to our west is also named Franklin. So, giving a citation to "Franklin" but omitting the political subdivision is certainly confusing if citing an event in this area. > > Bottom line: I have 8666 locations in my database. Average length is 27 with a standard deviation of 9. Largest location has 98 characters with only 10 having a length of 70 or more (and those 10 could have been shortened by abbreviations if I saw the value is so doing. > > Jim Ramaley > Gettysburg, PA > > If all the fields in BK are at the max allowed by GEDCOM, ( http://www.phpgedview.net/ged551-5.pdf ) I suggest leaving them alone. Much data is swapped with others around the globe who may be using some other program than BK. IMHO it would seem that GEDCOM is the deciding factor on field length.
I am currently working with my original database on the left and a database which was the result of a gedcom from one of my common DNA relatives on the right. The right side has numerous new people which I need to move to the left. The compare routine doesn't find these people. I am seeking the best way to identify the candidates to acquire into my original database. If there is something I am missing please advise how. The only way I have figured out is to run the routine with the new database on the left, but that doesn't provide for a way to move the people, only provides for identifying the ones that I have to go back to with the databases back in the original position. Got to be an easier way to compare right to left. Dick Rose dtrose@cox.net
Otto, Please read my note more carefully before you fire off your typically negative comment. Your "subject for subject" comment after your "etc" in item 7 is strange. I had TWO suggestions. You have 7, well actually only 6, sections -- none of which address my main point that the source citation fields be used for further detail if desired. 1. You are in agreement with me that one should use abbreviations IF they are not confusing. What point are you trying to make that is different from mine? In my case of 8600 locations I had only 1 what was even close to the maximum -- and I have now reviewed it and changed it to be more readable -- and shorter! 2. Why should BK substitute for a history book? There are examples even here in Pennsylvania of some locations having been in as many as 6 counties at different times in history. Should I list all six in the location field? If in compiling a genealogy you want to include a chapter on history or on geography you can easily do so and it will be more complete and more readable than trying to fit it into a 100-character (or even 200-character!) location field. 3. My point exactly. So what is the point of your comment? 4. See number 2. Why keep beating a dead horse. 5. I have over 8000 locations. There are only a few that someone would have trouble locating. Why set up GPS for every location? If GPS is important for a specific location, use a source citation field and put it in. Are you going to search on GPS so that it needs to be a separately indexed field? 6. Your BK must work differently than mine. I can put in a partial location and F8 supplies candidates just like *. Without the *. Nowhere do I say that John should stop development. I said that I am against structural changes if there are good alternatives. I have often found that thoughtful users can themselves suggest work arounds and I have seen many suggestions from readers of this forum that do just that My opinion on avoiding structural changes is based upon a career in programming and systems design, and the managing of teams of such people. I stand by it. There are times when a structural change is required, but it is a tool of last resort, not of first resort. Jim Ramaley ----- Original Message ----- From: Otto Jørgensen To: bk@rootsweb.com Sent: Sunday, May 27, 2012 5:42 AM Subject: Re: [BK] Number of Characters Allowed On Fri, 25 May 2012 23:16:11 -0400, "Jim Ramaley" <jramaley@comcast.net> wrote: >John, > >I am not in favor of structural changes to a program to accommodate a perceived need when that need can be easily handled with a work-around. > >The issue seems to be that folks want to use the Location field in ways that were not intended. > >For example, some want it to be a history lesson by including former names of a location. I recall seeing one some years ago who wanted to include the fact that many current-day European locations were, historically, part of the Holy Roman Empire. > >Some want the location to be GPS exact and while that might be technically possible today, it is not nearly as useful as saying something like "Schlosser's Church, Unionville/Neff, North Whitehall Twp, Lehigh Co, PA . > >I use the location field to help a reader or fellow researcher in understanding enough of the location of a given event to visit or to do further research. When I go into the field I find that your report "Locations with Events" to be of great value. But if locations were so specific that they are unique to a given individual, this report would be much less useful. > >There are at least two ways that greater precision can be given in specifying the location for an event. > >1. Events have a source field. The source screen has several fields > that could be populated to make the citation more geographically > precise. For example, if one wants to specify the section, lot, > and plot number for a grave, there are comment fields, text > fields, and page / reel number fields [that's what I use]. These > print out on reports and you would want to cite a source anyway. > >2. If a location has "changed" because of political activity (example: > a new county is formed out of an old one) it usually takes only a > few characters out of the 100 available to so indicate. For > example, I have ancestors buried in what is now Lehigh County, PA, > but at the time of the probate of the wills the county was > Northampton. If necessary for understanding, I use "Heidelberg > Twp, Lehigh (formerly Northampton) Co, PA" > >I have read that some folks don't want to use abbreviations because they can be confusing. I have found that to be the case only where the political subdivision is not known to the researcher and has been left blank. For example, here in Adams County, PA the westernmost township is Franklin Twp. The next county to our west is also named Franklin. So, giving a citation to "Franklin" but omitting the political subdivision is certainly confusing if citing an event in this area. > >Bottom line: I have 8666 locations in my database. Average length is 27 with a standard deviation of 9. Largest location has 98 characters with only 10 having a length of 70 or more (and those 10 could have been shortened by abbreviations if I saw the value is so doing. > I don't agree mostly. I firstly say that fields are used for what they are specified!! 1. If I have a very long name as specified in a previous answer I see the Idea to shorten that for the reader, but I agree that it is also necessary to give the complete name of location. The example was 108 characters and for me I think that is to long in a book. If you repeat that name of location several time, for all events on the same page (born, birth, marry, death, education etc) My idea was to use a short abr. in the text and have a common footnotes down on the same page telling the complete name. Paper used has normal limit of 112 characters on a line. 2. Names is necessary to also give the political history. Many Norwegian have roots from Sweden and some of the location that now is Swedish was earlier Norwegian. This is normal and similar in many countries http://en.wikipedia.org/wiki/J%C3%A4mtland The sources here is to be found in both Norway and Sweden and have to be specified and it is a need for the reader to understand that. So there is a need to have soma information. W can put that in the detail of Location. It is waist of time and paper to tell this several places in a biography of the family BK has not yet any good way to connect places, nor when they have new administration or changed name Sankt Petersburg = Petrograd = Leningrad For names on person we have a lot of Alternatives names. That seems to be OK, but not for location. For Persons and events we use biography and Notes, but not for Location (here we shall put that information into the biography under Edit or as Note)? To add storry of farms we normaly use http://www.dokpro.uio.no/rygh_ng/rygh_form.html http://www.dokpro.uio.no/perl/navnegransking/rygh_ng/rygh_visetekst.prl?s=e&Vise=Show&KRYSS128347@29149=on and that is sources for our farms with different way of naming/spelling farm-names 3. Many do want to include the history of a farm, a church etc to the history of a family. In stead of repeating this all the time for many persons in the family book you can add that once place and use that in the same way you make index 4. A location can beside change country as a result if was WWII also have different administration whether it is Civil or religion. The borders for the administration are different even in the same countries. 5. GPS is great and we can add coordinates to BK, even if the program not yet have the map connection. But we must also thing forward and not stop thinking of new ideas. 6. Search methods For name we can use * and ? to find the name directly. It is not perfect, but we have only F8 for location. On both we should be able to use the function "including" 7. Etc So I can continue with subject for subject. It is good future to have the possibility in the program, but that does not mean that everybody do have to use them all. And that is up to you to enter information into the program and it is up to you to use the possibilities. We can not tell users to not use the modern technique. We must hope that John can add it and give us the option to use the program, also in the future. It is also important that there will come new users, younger than we oldies will take the program forward to new generation. To stop developing the program is a bad idea -- 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
Thanks for all the thoughts on the this matter. And thank you, John, for explaining the difficulty of changing the number of characters allowed. We each have our own needs and ways of doing our genealogy. When I need more room, I will add the event twice so it will appear: Buried: 12 Nov 1800 at Stainland, Yorkshire, England Buried: in Providence United Reformed Church Cemetery, Beestonley Lane, Section 3 , Lot 387 Does anyone see any problem with this? Carole
You could change the second buried to interred. Looks nice * smiles to you* Patricia From: Carole Edwards Caruso Sent: Sunday, May 27, 2012 6:29 AM To: bk@rootsweb.com Subject: Re: [BK] Number of Characters Allowed Thanks for all the thoughts on the this matter. And thank you, John, for explaining the difficulty of changing the number of characters allowed. We each have our own needs and ways of doing our genealogy. When I need more room, I will add the event twice so it will appear: Buried: 12 Nov 1800 at Stainland, Yorkshire, England Buried: in Providence United Reformed Church Cemetery, Beestonley Lane, Section 3 , Lot 387 Does anyone see any problem with this? Carole 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
Updated and have not moved files to another location. On Fri, May 25, 2012 at 8:06 AM, Otto Jørgensen <otjoerge@online.no> wrote: > On Fri, 25 May 2012 07:58:35 -1000, Palekaiko <palekaiko@gmail.com> > wrote: > >>I am running BK 6.5.11 on Windows XP Pro. I almost never get any >>error messages, when suddenly yesterday, while backing up, I received >>Error 53. It appears that I have a txt file that is not associated >>with an individual. I see the text file and it appears to be >>associated with the proper picture which is associated with the proper >>individual. Suggestions as to how to correct this, please. >> > > Error 53 Path/file not found > > Have you updated your program lately ? > Haveyou moved some of your file to other location on your PC? > > Where are your database located (see on the fronpage of your program) > -- > 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
On Fri, 25 May 2012 23:22:27 +0100, "J. P. Gilliver (John)" <G6JPG@soft255.demon.co.uk> wrote: Do not forget that BK is used in many countries and what is OK in US is not necessary ok in Europe -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON
On Fri, 25 May 2012 17:14:42 -0400, Jim Mayor <jasmayor@gmail.com> wrote: >In addition I am a firm believer in abbreviations, e. g., RootsWeb >designated >abbreviations: >http://www.rootsweb.ancestry.com/~rigenweb/abbrev.html . I realize >that not everyone who might look at my data is American or even >familiar with these abbreviations, but everyone has access to >RootsWeb. Although I seldom use tree-formats for genealogy the use >of abbreviations and minimal location designations help keep those >things clean and compact. > Remember - Use the Archives at http://archiver.rootsweb.ancestry.com/cgi-bin/search do not forget that that list is based on English speaking People. It will be quicte different in all other alanguage And this is mostly outside the question of handling location in BK, both present an version in the closer future -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON
In message <db20s7ls6hdko23ok31f1u6apccdkri938@4ax.com>, Otto Jørgensen <otjoerge@online.no> writes: >On Fri, 25 May 2012 23:22:27 +0100, "J. P. Gilliver (John)" ><G6JPG@soft255.demon.co.uk> wrote: > > >Do not forget that BK is used in many countries and what is OK in US >is not necessary ok in Europe Do not forget that I am in UK, and very aware of assorted languages etcetera. -- J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf "To YOU I'm an atheist; to God, I'm the Loyal Opposition." - Woody Allen
In message <4fbff657.27ddb60a.6992.76ec@mx.google.com>, Jim Mayor <jasmayor@gmail.com> writes: >I have much sympathy for John Steed here. I am sure that the only >solution would be variable item lengths, which is possible, but would >involve a great deal of work. And even then I suspect that John >would find that there was something else wanted (and I could suggest several!). I suspect we all could! > >Personally, I take the approach of minimizing information, including >location, e. g., for burial I would just put in town, county, state >and country. (When this approach is consistent then words like >"county" aren't needed.) Then I use the "Notes" for refining >details. This is particularly advisable when there are name changes. As I do. Not just name changes - some places "move" into another county (especially if new counties are created, and then disappear again), or even (e. g. a lot of Poland) country. It is always a vexed question whether to use the name as it is now (which makes it easy to match places) or as it was (which is historically more accurate), and you'll find people who will defend each approach vigorously (-:. > >In addition I am a firm believer in abbreviations, e. g., RootsWeb >designated >abbreviations: >http://www.rootsweb.ancestry.com/~rigenweb/abbrev.html . I realize >that not everyone who might look at my data is American or even >familiar with these abbreviations, but everyone has access to >RootsWeb. Although I seldom use tree-formats for genealogy the use >of abbreviations and minimal location designations help keep those >things clean and compact. If there are indeed acknowledged lists, then I suppose something the long-suffering John could implement would be drop-downs, which could be expanded when printed (or whatever): these would have to allow for the addition of names not in the list, though. People in the various countries could contribute the lists, as (I think) they do with the translation files. [] -- J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf "... four Oscars, and two further nominations ... On these criteria, he's Britain's most successful film director." Powell or Pressburger? no; Richard Attenborough? no; Nick Park!
John, I am not in favor of structural changes to a program to accommodate a perceived need when that need can be easily handled with a work-around. The issue seems to be that folks want to use the Location field in ways that were not intended. For example, some want it to be a history lesson by including former names of a location. I recall seeing one some years ago who wanted to include the fact that many current-day European locations were, historically, part of the Holy Roman Empire. Some want the location to be GPS exact and while that might be technically possible today, it is not nearly as useful as saying something like "Schlosser's Church, Unionville/Neff, North Whitehall Twp, Lehigh Co, PA . I use the location field to help a reader or fellow researcher in understanding enough of the location of a given event to visit or to do further research. When I go into the field I find that your report "Locations with Events" to be of great value. But if locations were so specific that they are unique to a given individual, this report would be much less useful. There are at least two ways that greater precision can be given in specifying the location for an event. 1. Events have a source field. The source screen has several fields that could be populated to make the citation more geographically precise. For example, if one wants to specify the section, lot, and plot number for a grave, there are comment fields, text fields, and page / reel number fields [that's what I use]. These print out on reports and you would want to cite a source anyway. 2. If a location has "changed" because of political activity (example: a new county is formed out of an old one) it usually takes only a few characters out of the 100 available to so indicate. For example, I have ancestors buried in what is now Lehigh County, PA, but at the time of the probate of the wills the county was Northampton. If necessary for understanding, I use "Heidelberg Twp, Lehigh (formerly Northampton) Co, PA" I have read that some folks don't want to use abbreviations because they can be confusing. I have found that to be the case only where the political subdivision is not known to the researcher and has been left blank. For example, here in Adams County, PA the westernmost township is Franklin Twp. The next county to our west is also named Franklin. So, giving a citation to "Franklin" but omitting the political subdivision is certainly confusing if citing an event in this area. Bottom line: I have 8666 locations in my database. Average length is 27 with a standard deviation of 9. Largest location has 98 characters with only 10 having a length of 70 or more (and those 10 could have been shortened by abbreviations if I saw the value is so doing. Jim Ramaley Gettysburg, PA ----- Original Message ----- From: John Steed To: bk@rootsweb.com Cc: carolec@stny.rr.com Sent: Friday, May 25, 2012 2:17 PM Subject: Re: [BK] Number of Characters Allowed To Carole Edwards Caruso It has been suggested by a couple people for me to have longer locations in a future version. The current fields sizes are listed on page 68 in the BK 6.5 book. Those sizes are what I set up when I designed the data files. I can not change them without creating new data files for a different version of BK in the future. Back in the old days of BK 4, I had 40 characters for locations. When I changed it to 100 I thought that would make everyone happy. If I change it to 150 in the future, I am sure someone will want 200 later on. If I make the maximum 200 or 500 or some large number, then the data files will be larger for everyone, so that is why I picked 100 for BK 6 I am sorry that what you want to type does not fit in 100. You can attach a source to the event or attach a note to the event or attach a note to the location. You may need to abbreviate the location to make it fit in 100 characters. I will try to make it at least 150 characters long the next time I change the data file structure. John Steed ----- Original Message ----- From: "Carole Edwards Caruso" <carolec@stny.rr.com> To: <bk@rootsweb.com> Sent: Friday, May 25, 2012 9:43 AM Subject: [BK] Number of Characters Allowed >I need over the 100 characters allowable in Location for > Events. By the time I put in the name of the church, town, > county, country, location, section number, and grave number, > I have run out of my 100 characters. I see that when a > report is printed, the allowable 100 characters run over > into a second line. > > John, can we have the rest of that line so we could add > more description? There is all this empty space just waiting > to be filled. > > Is anyone else having this problem? > > Thanks for any consideration, John. > > Carole > > 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 > 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