On Fri, 25 May 2012 21:32:19 +0100, "J. P. Gilliver (John)" <G6JPG@soft255.demon.co.uk> wrote: >(As I've mentioned before, I wish I'd used the inverse order - country >first - so that a listing by location put all the England locations >together, rather than putting Newcastle, Northumberland, England, next >to New York, New York, USA.) that is question of technique Scandinavian use mostly use Oslo Norway Gøteborg, Sweden New York USA and if we are in our own countries we do not tell that we are in Norway. To search for a country whether the land is first or last is only a question of technique -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

On Fri, 25 May 2012 15:37:49 -0400, Geoffrey Wilson <glw4@psu.edu> wrote: >I am still using BK5g,, as did my late wife. Thus we were quite >limited in the amount of space we could use for locations. >Our ancestry is nearly all in England, so I used the Chapman County >Codes as abbreviations, which was common practice there. >New codes were added following the 1974 redistricting., and are >contained in BS 6879:1987.// There is a good commentary in >http://www.coxresearcher.com/definitions/admin.htm . > >For Canadian provnces I use the two-letter abbreviations used by Canada Poste. >For the USA I use the two-letter abbreviations of the US Postal Service. I did have over 1700 external text files I BK5 and there was also limits in Events and location and so son. So the version of BK6 and later all updates/upgrades has been large steps forwards both to making reports/books and also to connect pictures and sources and have proper link to web pages and so on. So return back to BK 5 is to return to start of our history and to forget all what is available of sources and information and new technology -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

In message <1337971268.45401.YahooMailClassic@web162104.mail.bf1.yahoo.com>, Marsha Ensminger <marshaensminger@yahoo.com> writes: >John, > >If you're considering a change to the file structure, I would suggest a >radical change. Break up the single location field into multiple >fields, as "The Master Genealogist" does. Can I second this one? I use hierarchical with commas - for Britain, I use town (or village), county, country, with anything below town (e. g. house number and street name) in the comment field. I do this so that if I create a listing by location, events in the same town/village come together - if I included the house number and street in the location field, then any listing by location would have hundreds of locations, each with only one or two events in it. For USA/Canada locations, I use town (or whatever), state/province, country. (As I've mentioned before, I wish I'd used the inverse order - country first - so that a listing by location put all the England locations together, rather than putting Newcastle, Northumberland, England, next to New York, New York, USA.) [] >Of course, if you were to break up the location field there would be >issues in converting "old" BK data to the "new" format. TMG's import I suppose there could be a tickbox to select between the two formats, with the default for new entries being one of the configurable options. >routine did a pretty good job of separating the component parts and >assigning them to the appropriate fields. I suspect the commas I used >had something to do with it. Did/do you enter blank commas for unknown details (so, for my scheme, if all you knew was that it was England, you'd put ", , England")? > >Also of course, whatever labels you assign to the various fields will >cause dissension among users. What works for me won't please Otto... I >don't know if there's a way for you to structure them as "field 1", >"field 2", and so on and then allow the individual users to add names >that make sense to them. Though that could be done by manipulating the language file, as discussed (for some other reason) here recently. > >Marsha L. Ensminger > > >--- On Fri, 5/25/12, John Steed <brothers_keeper@msn.com> wrote: > >> From: John Steed <brothers_keeper@msn.com> [] >> files.  I can not >> change them without creating new data files for a different >> version of BK in >> the future. (Should you ever do this, perhaps a non-fixed length - with a size byte/doublebyte and/or a null-terminator - might avoid the need four even further changes, until people want more than 64K characters anyway!) [] -- J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf Live Faust, die Jung.

On Fri, 25 May 2012 11:41:08 -0700 (PDT), Marsha Ensminger <marshaensminger@yahoo.com> wrote: >John, > >If you're considering a change to the file structure, I would suggest a radical change. Break up the single location field into multiple fields, as "The Master Genealogist" does. > >I got so frustrated by the 40 character back in the "old" days that I went looking for an alternative. I have yet to come up with a location that TMG can't handle. > >Of course, if you were to break up the location field there would be issues in converting "old" BK data to the "new" format. TMG's import routine did a pretty good job of separating the component parts and assigning them to the appropriate fields. I suspect the commas I used had something to do with it. > >Also of course, whatever labels you assign to the various fields will cause dissension among users. What works for me won't please Otto... I don't know if there's a way for you to structure them as "field 1", "field 2", and so on and then allow the individual users to add names that make sense to them. > For a location you might also to include information about that, So my idea is to have a attachment in the same way as for sources. To this attachment (appendix) can have a discription or more about the location, add a photo or similar. Here the full nam,e and the variation about names, when location has different names during timeline, war, cahange of counbtries et. All this can be made once in the Apendix and from all place in a book, report or what ever the reference can goes to this appendix. It will save space and make the family book, reports more readable and nice. And there is on ly one place at BK to make all update of history. Every countries has similar history, Even USA has different history on many location. In Eurpoe we have the same, e.g. West and East Germany, Polen, Denmark, Norway, Sweden. To make that part of out familyhistory connected to places, farms, town etc gives a more nice presentation. -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

On Fri, 25 May 2012 11:07:10 -0700 (PDT), Marsha Ensminger <marshaensminger@yahoo.com> wrote: >My readers are not necessarily Americans. >Abbreviations like "Cty" may not be understood. > >Abbreviations are much too likely to introduce misunderstandings, >misreadings, and errors. I'm old enough to remember when "Ia" was a >perfectly acceptable abbreviation for Indiana. Then the USPS decided >that Indiana should be "IN", and Iowa "IA". So now, according to >ancestry.com's census transcribers, thousands of native Indianans who >may never have traveled as far west as Illinois are recorded as having >been born in Iowa. > >The location only occurs once per individual; I don't think that makes for overly long reading. > Abbreviation can be used without problem if there is a notification to the abbr. in the report. It can be used as I did mention earliger. E.G. we often do this for sources so why not sometimes also for location. It is only a question to find the best way to abbr. and to have the program to take care of both the Abbr. and the completely full name. -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

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

I put the address in the Location field and the other details in Notes for that entry. You can have the notes print every time. David Youse Effectus bonus addo bonus On May 25, 2012, at 1:02 PM, bk-request@rootsweb.com wrote: > To all Digest receivers: There are two forms of the "Digest" differing in appearance. The default is "Plain" and the other choice is "MIME" - if you would like to try the other view send a private message to me at listutilities@cox.net > Today's Topics: > > 1. Number of Characters Allowed (Carole Edwards Caruso) > 2. Re: Number of Characters Allowed (Otto J?rgensen) > 3. Re: Number of Characters Allowed (Otmar Mayr) > 4. Re: Number of Characters Allowed (Jim Dell) > 5. Re: Number of Characters Allowed (Otmar Mayr) > 6. Re: Number of Characters Allowed (Otto J?rgensen) > 7. Re: Number of Characters Allowed (Marsha Ensminger) > 8. Re: Number of Characters Allowed (Otto J?rgensen) > 9. Number of Characters Allowed (Rick Beitler) > 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 > > On Fri, 25 May 2012 09:43:54 -0400, "Carole Edwards Caruso" > <carolec@stny.rr.com> wrote: > >> 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? >> > > do you not use the sourc elements > and > Do you double click on the location anem to add detail of location > there > > The church yard are the place and in av way the main source, > The gravenumber is a detals related to the gravyeard > > > It is nearly as the Churchbook are the main source but the page and > line in the churcbook are details connected to the main source. > > An other question: > Will you every grave prin t all those long refernces each time? > -- > Otto Jørgensen > http://www.bkwin.info/ > All email is checked by NORTON > > > > Hello! > > On Friday, May 25, 2012 Carole Edwards Caruso wrote in [BK]: > > CEC> I need over the 100 characters allowable in Location for > CEC> Events. By the time I put in the name of the church, town, > CEC> county, country, location, section number, and grave number, > CEC> I have run out of my 100 characters. I see that when a > CEC> report is printed, the allowable 100 characters run over > CEC> into a second line. > > CEC> John, can we have the rest of that line so we could add > CEC> more description? There is all this empty space just waiting > CEC> to be filled. > > CEC> Is anyone else having this problem? > > CEC> Thanks for any consideration, John. > > CEC> Carole > > I wrote John in December 2009 about this problem. Perhaps we get now a > expansion to 150 characters. > > -- > Otmar Mayr > > > > > -----Original Message----- > From: bk-bounces@rootsweb.com [mailto:bk-bounces@rootsweb.com] On Behalf Of > Otto Jørgensen > Sent: Friday, May 25, 2012 10:13 AM > To: bk@rootsweb.com > Subject: Re: [BK] Number of Characters Allowed > > On Fri, 25 May 2012 09:43:54 -0400, "Carole Edwards Caruso" > <carolec@stny.rr.com> wrote: > >> 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? >> > > do you not use the sourc elements > and > Do you double click on the location anem to add detail of location there > > The church yard are the place and in av way the main source, The gravenumber > is a detals related to the gravyeard > > > It is nearly as the Churchbook are the main source but the page and > line in the churcbook are details connected to the main source. > > An other question: > Will you every grave prin t all those long refernces each time? > -- > Otto Jørgensen > http://www.bkwin.info/ > All email is checked by NORTON > > > Otto, > What's the GEDCOM standard say the max length for locations is? > > Jim > > > > Hello Otto! > > On Friday, May 25, 2012 you wrote in [BK]: > > OJ> On Fri, 25 May 2012 09:43:54 -0400, "Carole Edwards Caruso" > OJ> <carolec@stny.rr.com> wrote: > >>> I need over the 100 characters allowable... > > OJ> do you not use the sourc elements > OJ> and > OJ> Do you double click on the location anem to add detail of location > OJ> there > > OJ> The church yard are the place and in av way the main source, > OJ> The gravenumber is a detals related to the gravyeard > > > OJ> It is nearly as the Churchbook are the main source but the page and > OJ> line in the churcbook are details connected to the main source. > > OJ> An other question: > OJ> Will you every grave prin t all those long refernces each time? > > I use the notes for places for additional information. But with that I cannot solve my problem. > > The place names are hierarchical in six parts. Here is an example of > the field: > > Cemetery St. Anton, Hohenems, Vorarlberg, Gefürstete Grafschaft Tirol, Kaisertum Österreich, Deutscher Bund > > Because this place name exceeds the 100 characters, it is necessary to > cut the last part. I need this structure for the list of places on my > website (www.verwandten.info). In "Familienbücher" (Adelige Familien) > you can see how are organized the places hierarchically. I handle the > problem, with using of the search-replace function. But this is an > annoying extra work. > > -- > greetings, Otmar Mayr > > > On Fri, 25 May 2012 17:53:21 +0200, Otmar Mayr <om6923@gmail.com> > wrote: > >> Hello Otto! >> >> On Friday, May 25, 2012 you wrote in [BK]: >> >> OJ> On Fri, 25 May 2012 09:43:54 -0400, "Carole Edwards Caruso" >> OJ> <carolec@stny.rr.com> wrote: >> >>>> I need over the 100 characters allowable... >> >> OJ> do you not use the sourc elements >> OJ> and >> OJ> Do you double click on the location anem to add detail of location >> OJ> there >> >> OJ> The church yard are the place and in av way the main source, >> OJ> The gravenumber is a detals related to the gravyeard >> >> >> OJ> It is nearly as the Churchbook are the main source but the page and >> OJ> line in the churcbook are details connected to the main source. >> >> OJ> An other question: >> OJ> Will you every grave prin t all those long refernces each time? >> >> I use the notes for places for additional information. But with that I cannot solve my problem. >> >> The place names are hierarchical in six parts. Here is an example of >> the field: >> >> Cemetery St. Anton, Hohenems, Vorarlberg, Gefürstete Grafschaft Tirol, Kaisertum Österreich, Deutscher Bund >> >> Because this place name exceeds the 100 characters, it is necessary to >> cut the last part. I need this structure for the list of places on my >> website (www.verwandten.info). In "Familienbücher" (Adelige Familien) >> you can see how are organized the places hierarchically. I handle the >> problem, with using of the search-replace function. But this is an >> annoying extra work. > > Your location is 108 > > I might remeber wrong but did think the lenght of location was 120 > > I believe John will give the correct answer. > -- > Otto Jørgensen > http://www.bkwin.info/ > All email is checked by NORTON > > > > Even without a precise grave location, I'm in trouble with > St. Paul Evangelical & Reformed (now United Church of Christ) Cemetery (Bluff Road), Edwardsville, Madison County, Illinois. > > And yes, I do want all that to print every time. I'm still trying to differentiate among the various "St. Paul" churches in the neighborhood referred to by an earlier researcher. She knew which one she meant, but it's not at all clear to me. > > Marsha L. Ensminger > > > --- On Fri, 5/25/12, Carole Edwards Caruso <carolec@stny.rr.com> wrote: > >> From: Carole Edwards Caruso <carolec@stny.rr.com> >> Subject: [BK] Number of Characters Allowed >> To: bk@rootsweb.com >> Date: Friday, May 25, 2012, 6:43 AM >> 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 >> > > > On Fri, 25 May 2012 09:35:37 -0700 (PDT), Marsha Ensminger > <marshaensminger@yahoo.com> wrote: > >> Even without a precise grave location, I'm in trouble with >> St. Paul Evangelical & Reformed (now United Church of Christ) Cemetery (Bluff Road), Edwardsville, Madison County, Illinois. >> >> And yes, I do want all that to print every time. I'm still trying to differentiate >> among the various "St. Paul" churches in the neighborhood referred to >> by an earlier researcher. She knew which one she meant, but it's >> not at all clear to me. >> >> Marsha L. Ensminger >> > > > I believe John will give an answer. > > Do however rember that using so lon g name for location a report with > the same location mention several times will be large. > > And on e have to think if thjat isreadble for user to have those long > navmes repeated all the time. > > May be a shortant name and the total name as a footnote or appendix. > > This is a way similar to some ot the farmname, where we want to add > all previous names and the history. By we do not waht that to be > direct included in the resulta of edit but more as a appendix where we > also can include photoes of farms, church, graveyard etc etc > -- > Otto Jørgensen > http://www.bkwin.info/ > All email is checked by NORTON > > > > Marsha- > I understand your frustration. You do all this work, and want it to be just > so, and limited by the space given. > > The only thing I can suggest is cutting out spaces and abbreviate whenever > you can. And I know it will not look like you want it to on reports, but if > you are consistently consistent, your reads will understand your meaning: > > St.Paul Evangelical&Reformed(ie United Church of Christ) Cemetery(Bluff > Road), Edwardsville, Madison Cty, IL > > Rick Beitler > Springfield, MO > rabone@gmail.com > chertyrock.blogspot.com > > Preach the Gospel at all times and when necessary use words. ~Saint Francis > of Assisi > > > ---------- Forwarded message ---------- > From: Marsha Ensminger <marshaensminger@yahoo.com> > Date: Fri, May 25, 2012 at 11:35 AM > Subject: Re: [BK] Number of Characters Allowed > To: bk@rootsweb.com > > > Even without a precise grave location, I'm in trouble with > St. Paul Evangelical & Reformed (now United Church of Christ) Cemetery > (Bluff Road), Edwardsville, Madison County, Illinois. > > And yes, I do want all that to print every time. I'm still trying to > differentiate among the various "St. Paul" churches in the neighborhood > referred to by an earlier researcher. She knew which one she meant, but > it's not at all clear to me. > > Marsha L. Ensminger > > > --- On Fri, 5/25/12, Carole Edwards Caruso <carolec@stny.rr.com> wrote: > >> From: Carole Edwards Caruso <carolec@stny.rr.com> >> Subject: [BK] Number of Characters Allowed >> To: bk@rootsweb.com >> Date: Friday, May 25, 2012, 6:43 AM >> 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 > > To contact the BK list administrator, send an email to > BK-admin@rootsweb.com. > > To post a message to the BK mailing list, send an email to BK@rootsweb.com. > > __________________________________________________________ > 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 > email with no additional text.

On Fri, 25 May 2012 09:35:37 -0700 (PDT), Marsha Ensminger <marshaensminger@yahoo.com> wrote: >Even without a precise grave location, I'm in trouble with >St. Paul Evangelical & Reformed (now United Church of Christ) Cemetery (Bluff Road), Edwardsville, Madison County, Illinois. > >And yes, I do want all that to print every time. I'm still trying to differentiate >among the various "St. Paul" churches in the neighborhood referred to > by an earlier researcher. She knew which one she meant, but it's >not at all clear to me. > >Marsha L. Ensminger > I believe John will give an answer. Do however rember that using so lon g name for location a report with the same location mention several times will be large. And on e have to think if thjat isreadble for user to have those long navmes repeated all the time. May be a shortant name and the total name as a footnote or appendix. This is a way similar to some ot the farmname, where we want to add all previous names and the history. By we do not waht that to be direct included in the resulta of edit but more as a appendix where we also can include photoes of farms, church, graveyard etc etc -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

On Fri, 25 May 2012 17:53:21 +0200, Otmar Mayr <om6923@gmail.com> wrote: >Hello Otto! > >On Friday, May 25, 2012 you wrote in [BK]: > >OJ> On Fri, 25 May 2012 09:43:54 -0400, "Carole Edwards Caruso" >OJ> <carolec@stny.rr.com> wrote: > >>>I need over the 100 characters allowable... > >OJ> do you not use the sourc elements >OJ> and >OJ> Do you double click on the location anem to add detail of location >OJ> there > >OJ> The church yard are the place and in av way the main source, >OJ> The gravenumber is a detals related to the gravyeard > > >OJ> It is nearly as the Churchbook are the main source but the page and >OJ> line in the churcbook are details connected to the main source. > >OJ> An other question: >OJ> Will you every grave prin t all those long refernces each time? > >I use the notes for places for additional information. But with that I cannot solve my problem. > >The place names are hierarchical in six parts. Here is an example of >the field: > >Cemetery St. Anton, Hohenems, Vorarlberg, Gefürstete Grafschaft Tirol, Kaisertum Österreich, Deutscher Bund > >Because this place name exceeds the 100 characters, it is necessary to >cut the last part. I need this structure for the list of places on my >website (www.verwandten.info). In "Familienbücher" (Adelige Familien) >you can see how are organized the places hierarchically. I handle the >problem, with using of the search-replace function. But this is an >annoying extra work. Your location is 108 I might remeber wrong but did think the lenght of location was 120 I believe John will give the correct answer. -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

Hello Otto! On Friday, May 25, 2012 you wrote in [BK]: OJ> On Fri, 25 May 2012 09:43:54 -0400, "Carole Edwards Caruso" OJ> <carolec@stny.rr.com> wrote: >>I need over the 100 characters allowable... OJ> do you not use the sourc elements OJ> and OJ> Do you double click on the location anem to add detail of location OJ> there OJ> The church yard are the place and in av way the main source, OJ> The gravenumber is a detals related to the gravyeard OJ> It is nearly as the Churchbook are the main source but the page and OJ> line in the churcbook are details connected to the main source. OJ> An other question: OJ> Will you every grave prin t all those long refernces each time? I use the notes for places for additional information. But with that I cannot solve my problem. The place names are hierarchical in six parts. Here is an example of the field: Cemetery St. Anton, Hohenems, Vorarlberg, Gefürstete Grafschaft Tirol, Kaisertum Österreich, Deutscher Bund Because this place name exceeds the 100 characters, it is necessary to cut the last part. I need this structure for the list of places on my website (www.verwandten.info). In "Familienbücher" (Adelige Familien) you can see how are organized the places hierarchically. I handle the problem, with using of the search-replace function. But this is an annoying extra work. -- greetings, Otmar Mayr

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!). 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. 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.

Hello! On Friday, May 25, 2012 Carole Edwards Caruso wrote in [BK]: CEC> I need over the 100 characters allowable in Location for CEC> Events. By the time I put in the name of the church, town, CEC> county, country, location, section number, and grave number, CEC> I have run out of my 100 characters. I see that when a CEC> report is printed, the allowable 100 characters run over CEC> into a second line. CEC> John, can we have the rest of that line so we could add CEC> more description? There is all this empty space just waiting CEC> to be filled. CEC> Is anyone else having this problem? CEC> Thanks for any consideration, John. CEC> Carole I wrote John in December 2009 about this problem. Perhaps we get now a expansion to 150 characters. -- Otmar Mayr

On Fri, 25 May 2012 09:43:54 -0400, "Carole Edwards Caruso" <carolec@stny.rr.com> wrote: >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? > do you not use the sourc elements and Do you double click on the location anem to add detail of location there The church yard are the place and in av way the main source, The gravenumber is a detals related to the gravyeard It is nearly as the Churchbook are the main source but the page and line in the churcbook are details connected to the main source. An other question: Will you every grave prin t all those long refernces each time? -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

I am still using BK5g,, as did my late wife. Thus we were quite limited in the amount of space we could use for locations. Our ancestry is nearly all in England, so I used the Chapman County Codes as abbreviations, which was common practice there. New codes were added following the 1974 redistricting., and are contained in BS 6879:1987.// There is a good commentary in http://www.coxresearcher.com/definitions/admin.htm . For Canadian provnces I use the two-letter abbreviations used by Canada Poste. For the USA I use the two-letter abbreviations of the US Postal Service. At 02:17 PM 5/25/2012, John Steed wrote: >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

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 >

To Michael palekaiko@gmail.com Are you using BK 6.5 When you get the error, does it say the text file is attached to a person, marriage, or event? If a person, go to that person and go to the Notes tab. Is there more than one note attached there? John Steed ----- Original Message ----- From: "Palekaiko" <palekaiko@gmail.com> To: <BK@rootsweb.com> Sent: Friday, May 25, 2012 1:58 PM Subject: [BK] Error 53 >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. > > Michael > 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 >

Marsha- I understand your frustration. You do all this work, and want it to be just so, and limited by the space given. The only thing I can suggest is cutting out spaces and abbreviate whenever you can. And I know it will not look like you want it to on reports, but if you are consistently consistent, your reads will understand your meaning: St.Paul Evangelical&Reformed(ie United Church of Christ) Cemetery(Bluff Road), Edwardsville, Madison Cty, IL Rick Beitler Springfield, MO rabone@gmail.com chertyrock.blogspot.com Preach the Gospel at all times and when necessary use words. ~Saint Francis of Assisi ---------- Forwarded message ---------- From: Marsha Ensminger <marshaensminger@yahoo.com> Date: Fri, May 25, 2012 at 11:35 AM Subject: Re: [BK] Number of Characters Allowed To: bk@rootsweb.com Even without a precise grave location, I'm in trouble with St. Paul Evangelical & Reformed (now United Church of Christ) Cemetery (Bluff Road), Edwardsville, Madison County, Illinois. And yes, I do want all that to print every time. I'm still trying to differentiate among the various "St. Paul" churches in the neighborhood referred to by an earlier researcher. She knew which one she meant, but it's not at all clear to me. Marsha L. Ensminger --- On Fri, 5/25/12, Carole Edwards Caruso <carolec@stny.rr.com> wrote: > From: Carole Edwards Caruso <carolec@stny.rr.com> > Subject: [BK] Number of Characters Allowed > To: bk@rootsweb.com > Date: Friday, May 25, 2012, 6:43 AM > 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

John, If you're considering a change to the file structure, I would suggest a radical change. Break up the single location field into multiple fields, as "The Master Genealogist" does. I got so frustrated by the 40 character back in the "old" days that I went looking for an alternative. I have yet to come up with a location that TMG can't handle. Of course, if you were to break up the location field there would be issues in converting "old" BK data to the "new" format. TMG's import routine did a pretty good job of separating the component parts and assigning them to the appropriate fields. I suspect the commas I used had something to do with it. Also of course, whatever labels you assign to the various fields will cause dissension among users. What works for me won't please Otto... I don't know if there's a way for you to structure them as "field 1", "field 2", and so on and then allow the individual users to add names that make sense to them. Marsha L. Ensminger --- On Fri, 5/25/12, John Steed <brothers_keeper@msn.com> wrote: > From: John Steed <brothers_keeper@msn.com> > Subject: Re: [BK] Number of Characters Allowed > To: bk@rootsweb.com > Cc: carolec@stny.rr.com > Date: Friday, May 25, 2012, 11:17 AM > 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 >

My readers are not necessarily Americans. Abbreviations like "Cty" may not be understood. Abbreviations are much too likely to introduce misunderstandings, misreadings, and errors. I'm old enough to remember when "Ia" was a perfectly acceptable abbreviation for Indiana. Then the USPS decided that Indiana should be "IN", and Iowa "IA". So now, according to ancestry.com's census transcribers, thousands of native Indianans who may never have traveled as far west as Illinois are recorded as having been born in Iowa. The location only occurs once per individual; I don't think that makes for overly long reading. Marsha L. Ensminger --- On Fri, 5/25/12, Rick Beitler <rabone@gmail.com> wrote: > From: Rick Beitler <rabone@gmail.com> > Subject: [BK] Number of Characters Allowed > To: "Brothers Keeper List" <BK-L@rootsweb.com> > Date: Friday, May 25, 2012, 10:02 AM > Marsha- > I understand your frustration. You do all this work, and > want it to be just > so, and limited by the space given. > > The only thing I can suggest is cutting out spaces and > abbreviate whenever > you can. And I know it will not look like you want it to on > reports, but if > you are consistently consistent, your reads will understand > your meaning: > > St.Paul Evangelical&Reformed(ie United Church of Christ) > Cemetery(Bluff > Road), Edwardsville, Madison Cty, IL > > Rick Beitler > Springfield, MO > rabone@gmail.com > chertyrock.blogspot.com > > Preach the Gospel at all times and when necessary use words. > ~Saint Francis > of Assisi > > > ---------- Forwarded message ---------- > From: Marsha Ensminger <marshaensminger@yahoo.com> > Date: Fri, May 25, 2012 at 11:35 AM > Subject: Re: [BK] Number of Characters Allowed > To: bk@rootsweb.com > > > Even without a precise grave location, I'm in trouble with > St. Paul Evangelical & Reformed (now United Church of > Christ) Cemetery > (Bluff Road), Edwardsville, Madison County, Illinois. > > And yes, I do want all that to print every time.  I'm > still trying to > differentiate among the various "St. Paul" churches in the > neighborhood > referred to by an earlier researcher.  She knew which > one she meant, but > it's not at all clear to me. > > Marsha L. Ensminger > > > --- On Fri, 5/25/12, Carole Edwards Caruso <carolec@stny.rr.com> > wrote: > > > From: Carole Edwards Caruso <carolec@stny.rr.com> > > Subject: [BK] Number of Characters Allowed > > To: bk@rootsweb.com > > Date: Friday, May 25, 2012, 6:43 AM > > 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 > 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 >

-----Original Message----- From: bk-bounces@rootsweb.com [mailto:bk-bounces@rootsweb.com] On Behalf Of Otto Jørgensen Sent: Friday, May 25, 2012 10:13 AM To: bk@rootsweb.com Subject: Re: [BK] Number of Characters Allowed On Fri, 25 May 2012 09:43:54 -0400, "Carole Edwards Caruso" <carolec@stny.rr.com> wrote: >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? > do you not use the sourc elements and Do you double click on the location anem to add detail of location there The church yard are the place and in av way the main source, The gravenumber is a detals related to the gravyeard It is nearly as the Churchbook are the main source but the page and line in the churcbook are details connected to the main source. An other question: Will you every grave prin t all those long refernces each time? -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON Otto, What's the GEDCOM standard say the max length for locations is? Jim