At 10:12 PM 3/23/01 +0000, you wrote: >I would like to share some of the ancestory data I've collected with my >relatives. Since none of them are especially avid genealogy researchers >I've been looking for a simple way to show a person their direct ancestors, >where and when they were born and died, from present to twelve generations >ago in Europe. > >I've figured out how to create and use selection lists, however, the >reports I've tried all produce way too much information, it's a bit >overwhelming to the novice. >Is there a way to produce a simple report of no more than six pages , which >would satisfy someone's curiosity or provide a framework for more detailed >reports on specific brances if someone takes an interest? One that I like is the 6 generation Ancestor Tree. However, it does only allow one line of data - which I normally use the one showing birth and death dates. This then, precludes showing a place name, however. But this does allow you to show up to 12 generations with a minimum number of pages. Ira ------------------------------------------------ Mr. Ira J. Lund E-mail: [email protected] Web: http://www.cf-software.com Cumberland Family Software, 385 Idaho Springs Road, Clarksville TN 37043

>Iv'e been using Ancestor list to generate reports. But I'm having only >limited sucess. > >I can never get more than three fields to print or output to file. There >seems to be no way to control field width on report output, so that more >fields are included. The CSV output doesn't provide for field selection. > >All I wanted was a list showing: > >Name, Birthplace, (birthyear-deathyear), Deathplace > >A simple request, that I can't get the program to accomplish. You are probably correct. Since the field widths can't be user adjusted, they are preset at certain sizes for a place field which - in the case above you have set 2 place fields and this may be wider than what the report will print. I think you are seeing all the available options and the program just can't support what you ask for. Allowing field width to be user adjusted would help. Ira ------------------------------------------------ Mr. Ira J. Lund E-mail: [email protected] Web: http://www.cf-software.com Cumberland Family Software, 385 Idaho Springs Road, Clarksville TN 37043

At 09:05 PM 3/25/01 +0000, you wrote: >It would be useful if CSV output allowed one to specify fields like the >report output does. It really does this. It's just different way to do it than in reports. What you do is create a selection list of events "Events to Include". Create a selection list of the events you want to export to CSV. >It would also be useful if the report output allowed one to specify the >field width so that more than three fields will print or output to text file. Sorry, no way to do this now. Will add to suggestion list. Ira ------------------------------------------------ Mr. Ira J. Lund E-mail: [email protected] Web: http://www.cf-software.com Cumberland Family Software, 385 Idaho Springs Road, Clarksville TN 37043

>The "Living" flag can be unchecked if you only know that a person has died, but if no further information is known about that person's death then all the information fields for the DEAT event will be blank. The "Living" flag is correctly handled for "empty" DEAT events in the "chart" type reports - if the flag is unchecked (deceased) then the line is present and simply reads "Death:", whereas if the flag is checked (living) then that line is blank - Thus showing that the person is alive or dead even though there is no further information to report. In the HTML output and other reports, where "blank" or "empty" events are suppressed, an unchecked living flag (deceased) does NOT cause the DEAT event to appear (albeit with no data). In other words, if the living flag is unchecked then otherwise "empty" DEAT events should be considered "non-empty". The same applies to the "story" (both screen and report). If the DEAT event is "non-blank" then the story reads "Name died <some dat! >a>.". If the DEAT event is "empty" and the flag is unchecked (deceased) then that sentence does NOT appear at all. I feel in this case the story should still read "Name died." - i.e. exactly the same wording, just with no data. Ok. Let me think about these issues and see what I can do. Ira ------------------------------------------------ Mr. Ira J. Lund E-mail: [email protected] Web: http://www.cf-software.com Cumberland Family Software, 385 Idaho Springs Road, Clarksville TN 37043

Dear Ira, when meandering through my database (1000+ IRNs) I always discover several tasks to be done before I miss them. I cannot complete them in parallel, thus it is necessary to make side notes - using different "StickIt" or "ToDo" freewares. My dream is to have a simple ToDo function integrated into CFTW (like I've seen in at least one other gene program). Keep developing your topping program! Best regards, Michal Jarocinski

It would be useful if CSV output allowed one to specify fields like the report output does. It would also be useful if the report output allowed one to specify the field width so that more than three fields will print or output to text file. I realize that I'm inexperienced with CFT so perhaps I'm missing something obvious. Can anyone offer a suggestion? Mike

Event notes do not show up in 'Story' output for children. Only if this child has a family of his/her own does the event note appear in the story of that family. The Story Options include an option for including Event Notes, but it has no effect on event notes for children. For example, I have many occurrences of children that died very young, and the only info I have is baptism info along with an extract from the baptismal registry, something like: "Witnes to this baptism were: blah, blah". I put this info in the Baptism Event Note, mostly because in some cases the extract is too long for "Miscellaneous". But, in story format this information is not displayed. Is there a solution to this?? Frank van Thienen Just getting started

Ancestral List Report only three fields get printed regardless of how small the font. Is there some way to change the field width so that more than three fields print? Mike

Hi Ira The "Living" flag can be unchecked if you only know that a person has died, but if no further information is known about that person's death then all the information fields for the DEAT event will be blank. The "Living" flag is correctly handled for "empty" DEAT events in the "chart" type reports - if the flag is unchecked (deceased) then the line is present and simply reads "Death:", whereas if the flag is checked (living) then that line is blank - Thus showing that the person is alive or dead even though there is no further information to report. In the HTML output and other reports, where "blank" or "empty" events are suppressed, an unchecked living flag (deceased) does NOT cause the DEAT event to appear (albeit with no data). In other words, if the living flag is unchecked then otherwise "empty" DEAT events should be considered "non-empty". The same applies to the "story" (both screen and report). If the DEAT event is "non-blank" then the story reads "Name died <some dat! a>.". If the DEAT event is "empty" and the flag is unchecked (deceased) then that sentence does NOT appear at all. I feel in this case the story should still read "Name died." - i.e. exactly the same wording, just with no data. John Smith South Africa

Hi All I only use the EMIG emigrate event, and specify (in the place name) where that person/couple emigrated "TO". The "FROM" is implied from the place where they were located before the move. Thus, in my opinion, the text "emigrated .. to .." is correct as it is in CFTW. John Smith South Africa

I would like to share some of the ancestory data I've collected with my relatives. Since none of them are especially avid genealogy researchers I've been looking for a simple way to show a person their direct ancestors, where and when they were born and died, from present to twelve generations ago in Europe. I've figured out how to create and use selection lists, however, the reports I've tried all produce way too much information, it's a bit overwhelming to the novice. Is there a way to produce a simple report of no more than six pages , which would satisfy someone's curiosity or provide a framework for more detailed reports on specific brances if someone takes an interest? Thanks, Mike

George, Thank you for incouraging informative discussion. > There were probably some users >of CFTW that didn't know they could edit the Events to do things >like change verbs, etc. > I am probably one of them, can you please explain how this is done with simple examples. The formatting 'wild card' symbols the advanced users illustrated only confused me. >Please, we went through a similar thread about a week ago and >I said at that time that we do not need to stifle discussion. >Regards, > >SgtGeorge I am still learning with ver3.05 so I don't know how much of the advanced ver3.06 immigrate-emigrate discussion applies to my case. When I was setting up my data base I needed a way to document the migrations which have played a significant role in my family's history. I looked at both IMMI and EMIG events and found the immigration confusing. After some experimentation I used EMIG with the destination in the Place field and the phrase "from Place" in the free format data field. An example story line reads: Andrew Ancestor emigrated in Date (from Hometown) to Place. This seems to work. is there a better way? Mike

Yes, I too tried to import my database from ver 2.50x to ver 3.06. Everything seemed to work fine except the place names. They were all wrong. walt boswell [email protected] ----- Original Message ----- From: "Gschneidinger Max" <[email protected]> To: <[email protected]> Sent: Friday, March 23, 2001 2:47 AM Subject: [CFTW] Ver 3.06 - place names > After various imports of my Ver 2.51 data to Ver 3.06 the place names in all cases did not import correctly. The import created a blank place name at index 1, so all the other place names were then out by one. Thus the place names for all the events were wrong. Before and after the import I run a rebuild. > > John Smith [[email protected]] confirmed to me that he had the same problem with Ver 3.06 whereas import in Ver 3.05 seemed to be o.k. The problem seems to have been introduced in 3.06. Has anybody else seen the same problem ? > Max > > Max Gschneidinger > [email protected] > http://worldroots.com/ged/max > > > ==== CFT-WIN Mailing List ==== > You can contact the List Manager at: > [email protected] > > ============================== > Search over 900 million names at Ancestry.com! > http://www.ancestry.com/rd/rwlist1.asp >

After various imports of my Ver 2.51 data to Ver 3.06 the place names in all cases did not import correctly. The import created a blank place name at index 1, so all the other place names were then out by one. Thus the place names for all the events were wrong. Before and after the import I run a rebuild. John Smith [[email protected]] confirmed to me that he had the same problem with Ver 3.06 whereas import in Ver 3.05 seemed to be o.k. The problem seems to have been introduced in 3.06. Has anybody else seen the same problem ? Max Max Gschneidinger [email protected] http://worldroots.com/ged/max

At 09:47 AM 3/23/01 +0100, you wrote: >After various imports of my Ver 2.51 data to Ver 3.06 the place names in all cases did not import correctly. The import created a blank place name at index 1, so all the other place names were then out by one. Thus the place names for all the events were wrong. Before and after the import I run a rebuild. > >John Smith [[email protected]] confirmed to me that he had the same problem with Ver 3.06 whereas import in Ver 3.05 seemed to be o.k. The problem seems to have been introduced in 3.06. Has anybody else seen the same problem ? Yes, everybody has seen this problem. Major bug that was introduced in 3.06 and will be fixed in 3.07. This one single bug will likely hasten me to release 3.07 as soon as aI can. Two solutions to this problem: 1. ZIp and e-mail your Ver 2 database to me and I'll convert it for you. 2. You can do a GED export in Ver 2 and then GED import in Ver 3. Sorry, Ira ------------------------------------------------ Mr. Ira J. Lund E-mail: [email protected] Web: http://www.cf-software.com Cumberland Family Software, 385 Idaho Springs Road, Clarksville TN 37043

----- Original Message ----- From: "Mike Calder" <[email protected]> To: <[email protected]> Sent: Thursday, 22 March 2001 13:11 Subject: Re: [CFTW] emigrate/immigrate > G'day , > > Mea culpa! > > Ira wrote:- > > I do recall some time ago (a year or more) someone told me that the way I > > had emigrate and immigrate events was totally backwards. I thought I > > checked and thought they were so I fixed it - I thought. Now I am being > > told that they are backwards again. So I double checked on a Web > dictionary and found: emigrate means to exit a country, immigrate means to enter a country What a noise about nothing. CFTW allows you edit the verb for any event, so alter it however it suits you best Gale

At 08:15 AM 03/22/2001, Ira J Lund wrote: *********START OF ORIGINAL MESSAGE TEXT********* >(snip) >My guess is that other programs are likely more careful than I have been >and will use the proper defination of emigrating "from" and immigrating >"to". > >Ira **********END OF ORIGINAL MESSAGE TEXT********** And that's another good reason to discuss subjects like this here on the Mailing List. We need to know these things! Regards, SgtGeorge George W. Durman Knoxville, TN

At 05:56 AM 03/22/2001, Gale Fursdon wrote: *********START OF ORIGINAL MESSAGE TEXT********* > > G'day , > > > > Mea culpa! > > > > Ira wrote:- > > > I do recall some time ago (a year or more) someone told me that the > way I > > > had emigrate and immigrate events was totally backwards. I thought I > > > checked and thought they were so I fixed it - I thought. Now I am > being > > > told that they are backwards again. So I double checked on a Web > > >dictionary and found: emigrate means to exit a country, immigrate > means to > > >enter a country > >What a noise about nothing. CFTW allows you edit the verb for any event, >so >alter it however it suits you best > >Gale **********END OF ORIGINAL MESSAGE TEXT********** It's not a "noise about nothing". It's by talking out things like this that we all learn something. There were probably some users of CFTW that didn't know they could edit the Events to do things like change verbs, etc. Please, we went through a similar thread about a week ago and I said at that time that we do not need to stifle discussion. Just remember that what seems like "noise about nothing" to some, may be an important bit of information to others, and, although we CAN edit Events, sometimes these discussions helps Ira in writing upgrades. Regards, SgtGeorge George W. Durman Knoxville, TN CFT-WIN List Administrator

G'day , Mea culpa! Ira wrote:- > I do recall some time ago (a year or more) someone told me that the way I > had emigrate and immigrate events was totally backwards. I thought I > checked and thought they were so I fixed it - I thought. Now I am being > told that they are backwards again. So I double checked on a Web dictionary > and found: > > emigrate means to exit a country > immigrate means to enter a country > > Thus my events should really say: > > %N emigrated from %P > %N immigrated to %P I must admit that I was the person that pointed Ira originally to the "error of his ways" ;-) Now that I check my DB in 3.05 I find that immigrants/emigrants are the wrong way round. I still have v 2.50 and checked against an old DB where they are correct. Being a pedantic bastard I have checked the Oxford (UK), WEBSTERS (1894 - USA) and the MACQUARIE (Australia). All use the definitions above. If one of the beauties of CFT is that it helps "write the book", please let us get it right. HURU, Mike CALDER http://members.optushome.com.au/mikecalder/ Researching: CALDER, DIXON, TUSON, GRACIE D&GFHS #2629

I agree with everyone that it is currently correct in vers 3.06 and should not be changed, however another similar confusion occurs with Departure/Arrival. I think departure is wrong eg. William departed April 10, 1826 at London Middlesex. Therefore I think it should read %N departed %D p{from} %P, likewise Arrival might read better with %N arrived %D p{in} %P. To confuse this even further it would be equally correct to say the following %N departed %D p{for} %P and likewise %N arrived %D p{from} %P. The question I have is that if we each change it to read in what we believe is correct English, how will GEDCOM handle it? Russell Hartnoll Auckland, New Zealand. >-----Original Message----- >From: Ira J Lund [mailto:[email protected]] >Sent: Wednesday, March 21, 2001 10:30 AM >To: [email protected] >Subject: [CFTW] emigrate/immigrate > > >I do recall some time ago (a year or more) someone told me that the way I >had emigrate and immigrate events was totally backwards. I thought I >checked and thought they were so I fixed it - I thought. Now I am being >told that they are backwards again. So I double checked on a Web dictionary >and found: > >emigrate means to exit a country >immigrate means to enter a country > >Thus my events should really say: > >%N emigrated from %P >%N immigrated to %P > >and I think they are the other way around. I wonder how many people I have >messed up with this. I think in Ver 3.07 I better set it straight (again). > >Ira > >