On Thu, 14 Feb 2013 14:42:25 GMT, Eagle@bellsouth.net (J. Hugh Sullivan) wrote: >On Thu, 14 Feb 2013 07:33:37 +0200, Steve Hayes ><hayesstw@telkomsa.net> wrote: > >>I use both. > >I use RootsMagic and Legacy the same way - or did. I found two >problems with transferring from one to the other. > >1. Both allow sourcing of names. But RM sources the name in a manner >that will not transfer back to Legacy as a name source. Instead it >transfers back by gedcom as "unassigned". The name is still sourced in >Legacy but the source is in the wrong place. > >2. Because I am known by my middle name I enclose my middle name in >quotes - and for everyone else who was known by the middle name. That >used to be very common years ago. It works in Legacy. RM picks it up >twice as... >Billy "Bob" "Bob" Doe. > Hugh, I guess I don't understand the part about RM picking it up twice. Do you mean if it's in quotes in Legacy, then GEDCOMed into RM, it picks the quoted name twice? (I don't have Legacy any more so I can't test that myself). If that's the case, then I think what is happening is that RM Thinks the quotes mean it's a nickname, which RM puts in quotes and includes when presenting the name. If you don't use nicknames, then it might be a fairly simple task to just remove all the nicknames after importing the GEDCOM into RM. After saying that, I'll admit I don't know how to do that (other then doing it on the GEDCOM), but ther's a guy that posts often to the RM mail list that has written lots of SQL scripts to operate on the Rm database, and I'm sure he could give some suggestions. > >After all these years I guess I will have to give up on RM. > >I tried PAF years ago and gave up on it quickly. Maybe I'll give it >another go as a second program to Legacy if gedcoms will transfer >precisely. > >Hugh

Denis Beauregard wrote: > On Wed, 13 Feb 2013 19:31:57 +0000, Ian Goddard > <goddai01@hotmail.co.uk> wrote in soc.genealogy.computing: > >>J. Hugh Sullivan wrote: >>> On Wed, 13 Feb 2013 11:30:01 -0500, Denis Beauregard >>> <denis.b-at-francogene.com@fr.invalid> wrote: >>> >>>> Personnally, I use LibreOffice so I can't comment about the >>>> ease of use of the freewares ! I write what I need with PHP. >>>> >>>> >>>> Denis >>> >>> Since you mentioned it... >>> >>> Can every document be saved as .doc and every spreadsheet as .xls? I >>> know they CAN be - but by default? >> >>Yes. Default settings are configurable at Tools>Options>Load/Save>General >> >>Word options available are 6.0, 95, 97/2000/XP/2003 2003/XML 2007/2010 >>XML in v 3.6.5. Excel are slightly different, 5.0 instead of 6.0 & also >>template options. I'm not sure about the new v 4.0. The usual warnings >>about non-native formats not necessarily representing what you see >>probably apply but I'm not sure if that's a real problem any more. > > I know at least one problem. I print CD pockets with LO and > I want to print the back and face parts vertically. It can > print only on the wrong direction in English (in French, it is > the opposite direction and it works correctly). I know there is an issue with portrait/landscape printing in LO. Workaround is to open the Print dialogue, select the Properties of the printer, and there in the Device settings change Printer Language type from PDF to Postscript (from driver). Maybe this helps also for you Herman Viaene -- Veel mensen danken hun goed geweten aan hun slecht geheugen. (G. Bomans) Lots of people owe their good conscience to their bad memory (G. Bomans)

singhals wrote: > Ian Goddard wrote: >> singhals wrote: %>< >> >> Easy. You only /copy/ them to the database. Don't delete the original. >> > > Newbies don't think of /that/. They scan thru FTM and save where-ever > it puts it. One copy, part of FTM. > >>> After the first few images were put in, most everyone discovered the >>> database was growing exponentially, >> >> If that were really the case something would be wrong. It should just >> grow linearly. > > You could be right, it's math after all, but 1 image tripled the file > size on my test. 1, 300 dpi scan of a 2x3 B&W photo. That depends on the size of the file before you added the image. How much bigger did the file grow in real terms. I'd expect it to grow by the size of the image plus whatever else went in there by way of title etc. & some indexing information. There is an other factor, however. It may well be that it starts off with a file of fixed size, mostly empty, adds data until it needs more room and then adds another fixed extent. It could even be that each time it keeps increasing the size of the extent ("They filled 4G? Right, this time we'll add 8G. That should keep them quiet for a while"). That's a good approach to space management; small databases stay within an initial small allocation but large databases get a generous allocation of space quickly and, provided there's a good sized empty block from which they can take their extents, don't end up in many scattered fragments which hurts performance. Each time the file extends it does so exponentially but this is offset by extending less frequently. In your case the acid test is what happens when you add a few more scans. Do you get to the point where you can add another scan or two without the file growing at all? %>< > > (G) But, you see, users don't think like developers. Users see "Store > images internally" and they think COOL! They don't think, "How many > images can I get on a 7G HD?" 7G? When did I last see a 7G disk? The first thing I did with this laptop was take out the 500G disk and drop in a 1Tb. Although in part this was to enable the 2nd thing which was to install Debian Linux without overwriting the original Win 7, just in case there was a problem & I had to take it back. %>< >> >> AFAICS what Gramps was originally doing was to simply note the path& >> filename of what you supplied. Only at export time did it take a copy. >> That would mean if you reorganised what you though was an >> outside-Gramps system it wouldn't have been able to find anything. >> >> BTW I installed the current version onto another Linux instance on a VM >> & tried running the import again. It still has the same default >> locations but will allow a merge. >> >> But I'd forgotten another of its little egregious features which is >> still there. Each database has a name, e.g. 1881Census. But by the >> time you've exported& reimported it's something like Family Tree 01 so >> you have to go through the lot renaming them. > > Ooops? Can't you change the code for the default to echo the file-name? That would be possible given that it's open source but there's an awful lot of Python code there so it was easier to just let it do its thing & fix it afterwards than try to understand what needed fixing where, especially as Python isn't one of my languages. -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk

On Tue, 12 Feb 2013 21:30:32 -0500, kraut / larry stark <kraut3852@yahoo.com> wrote: >Suggestions for a good freeware genealogy program that is not too >complicated. Brothers Keeper for windows, should fit the bill. Uncluttered, an easy learning curve. see http://www.bkwin.net/ Hope this helps, Cheers, Henry

Ian Goddard wrote: > singhals wrote: >> Ian Goddard wrote: >>> singhals wrote: > %>< >>> >>> Easy. You only /copy/ them to the database. Don't delete the original. >>> >> >> Newbies don't think of /that/. They scan thru FTM and save where-ever >> it puts it. One copy, part of FTM. >> >>>> After the first few images were put in, most everyone discovered the >>>> database was growing exponentially, >>> >>> If that were really the case something would be wrong. It should just >>> grow linearly. >> >> You could be right, it's math after all, but 1 image tripled the file >> size on my test. 1, 300 dpi scan of a 2x3 B&W photo. > > That depends on the size of the file before you added the image. How > much bigger did the file grow in real terms. I'd expect it to grow by > the size of the image plus whatever else went in there by way of title > etc.& some indexing information. > IIRCC, it was under 1m before the first image. > There is an other factor, however. It may well be that it starts off > with a file of fixed size, mostly empty, adds data until it needs more > room and then adds another fixed extent. It could even be that each > time it keeps increasing the size of the extent ("They filled 4G? > Right, this time we'll add 8G. That should keep them quiet for a > while"). That's a good approach to space management; small databases > stay within an initial small allocation but large databases get a > generous allocation of space quickly and, provided there's a good sized > empty block from which they can take their extents, don't end up in many > scattered fragments which hurts performance. Each time the file extends > it does so exponentially but this is offset by extending less > frequently. In your case the acid test is what happens when you add a > few more scans. Do you get to the point where you can add another scan > or two without the file growing at all? Couldn't say. It grew and grew with each of 5 images I added, none particularly large by my standards. I booted the experiment after the 5th image. At which time, it was taking about 20 minutes to just OPEN the thing. Color me, peeved? > %>< >> >> (G) But, you see, users don't think like developers. Users see "Store >> images internally" and they think COOL! They don't think, "How many >> images can I get on a 7G HD?" > > 7G? When did I last see a 7G disk? The first thing I did with this > laptop was take out the 500G disk and drop in a 1Tb. Although in part > this was to enable the 2nd thing which was to install Debian Linux > without overwriting the original Win 7, just in case there was a problem > & I had to take it back. > > %>< >>> >>> AFAICS what Gramps was originally doing was to simply note the path& >>> filename of what you supplied. Only at export time did it take a copy. >>> That would mean if you reorganised what you though was an >>> outside-Gramps system it wouldn't have been able to find anything. >>> >>> BTW I installed the current version onto another Linux instance on a VM >>> & tried running the import again. It still has the same default >>> locations but will allow a merge. >>> >>> But I'd forgotten another of its little egregious features which is >>> still there. Each database has a name, e.g. 1881Census. But by the >>> time you've exported& reimported it's something like Family Tree 01 so >>> you have to go through the lot renaming them. >> >> Ooops? Can't you change the code for the default to echo the file-name? > > That would be possible given that it's open source but there's an awful > lot of Python code there so it was easier to just let it do its thing& > fix it afterwards than try to understand what needed fixing where, > especially as Python isn't one of my languages. I heard _that_. There comes a time when getting it done is more valuable than understanding it. (g) Cheryl

On Thu, 14 Feb 2013 09:08:11 +1000, Henry Soszynski <royalty@iinet.com.au> wrote: >On Tue, 12 Feb 2013 21:30:32 -0500, kraut / larry stark ><kraut3852@yahoo.com> wrote: > >>Suggestions for a good freeware genealogy program that is not too >>complicated. > >Brothers Keeper for windows, should fit the bill. Uncluttered, an easy >learning curve. I thought that was shareware, not freeware. -- Steve Hayes from Tshwane, South Africa Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

On Wed, 13 Feb 2013 17:43:55 -0600, Charlie Hoffpauir <invalid@invalid.com> wrote: >On Wed, 13 Feb 2013 16:48:48 -0500, singhals <singhals@erols.com> >wrote: > >>Denis Beauregard wrote: >>> Le Tue, 12 Feb 2013 21:50:44 -0500, singhals<singhals@erols.com> >>> écrivait dans soc.genealogy.computing: >>> >> >>>> Legacy is a bit more complex and a lot prettier to look at. >>>> It has a free version. >>> >>> I would prefer Legacy over PAF because PAF is outdated. The >>> last release may be more than 10 years ago (or little changes >>> after that). Also, you have to be sure PAF will work on Win 7 >>> or 8, a problem with old softwares. >> >>Good grief, Denis! You'n'I are more'n 10 years old too, and >>I'd sooner my family didn't abandon me for a newer edition! ;) >> >>Cheryl > >LOL... In my view the only problem with PAF is that later editions >never lived up to PAF 2.3 There is that... and PAF 2.3 suffers from the Y2K bug -- Steve Hayes from Tshwane, South Africa Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

On Wed, 13 Feb 2013 11:30:01 -0500, Denis Beauregard <denis.b-at-francogene.com@fr.invalid> wrote: >I would prefer Legacy over PAF because PAF is outdated. The >last release may be more than 10 years ago (or little changes >after that). Also, you have to be sure PAF will work on Win 7 >or 8, a problem with old softwares. I use both. I use PAF 4 for quick 'n dirty rough research (and transfer the data files back and forth between my Win XP desktop and my Win 7 laptop every day. I use Legacy for my main family file with people that I'm fairly certain are related. PAF is easy for quick data entry. Legacy (even the free version) lets you seach on place names. Earlier versions of PAF (1 & 2) let you do that, but 4 & 5 don't. So for quick and easy stuff ("not too complicated"), try PAF. You can always move it to Legacy or another program later. -- Steve Hayes from Tshwane, South Africa Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

On Wed, 13 Feb 2013 16:48:48 -0500, singhals <singhals@erols.com> wrote: >Good grief, Denis! You'n'I are more'n 10 years old too, and >I'd sooner my family didn't abandon me for a newer edition! ;) > >Cheryl PAF is available to everyone. The standards we apply must be consistent. You knew I couldn't let that pass. Hugh

singhals wrote: > Ian Goddard wrote: >> Dennis Lee Bieber wrote: >>> On Tue, 12 Feb 2013 21:50:44 -0500, singhals<singhals@erols.com> >>> declaimed the following in soc.genealogy.computing: >>> >>>> kraut / larry stark wrote: >>>>> Suggestions for a good freeware genealogy program that is not too >>>>> complicated. >>>> >>>> If you're looking for MAC and free, don't believe there is one. >>>> >>>> If you're looking for unix based one, there is one, I just >>>> don't remember what it is; someone else will. >>>> >>> >>> Gramps http://gramps-project.org/ >>> >>> Should be usable on anything that can run a reasonably up-to-date >>> version of the Python language -- which includes Mac/Linux/Windows >>> (heck, some subsets of Python run on cell phones) >>> >> >> I rather fell out with Gramps after I upgraded to 3.3.1. Until that >> point I hadn't realised that it didn't keep copies of media files in its >> own database where, in my view, they should be kept. > > (G) Mostly to hold up the other end of the argument -- > FTM kept media in its internal database and most folks hated not having > access to the images from outside FTM. Easy. You only /copy/ them to the database. Don't delete the original. > After the first few images were put in, most everyone discovered the > database was growing exponentially, If that were really the case something would be wrong. It should just grow linearly. > and rather than reducing the number > of images they reduced the quality. I suppose this comes back to me having been a database developer working with an industrial-grade database engine. You want to keep bulky data? You allocate lots of space for it. > PAF5 like Gramps has you put the images into a separate directory; mine > are under PAF/Data/[dbname_img] and I finally got clever enough to put > the path into the NOTES > as a hedge against the next head-crash. AFAICS what Gramps was originally doing was to simply note the path & filename of what you supplied. Only at export time did it take a copy. That would mean if you reorganised what you though was an outside-Gramps system it wouldn't have been able to find anything. BTW I installed the current version onto another Linux instance on a VM & tried running the import again. It still has the same default locations but will allow a merge. But I'd forgotten another of its little egregious features which is still there. Each database has a name, e.g. 1881Census. But by the time you've exported & reimported it's something like Family Tree 01 so you have to go through the lot renaming them. -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk

On Wed, 13 Feb 2013 19:31:57 +0000, Ian Goddard <goddai01@hotmail.co.uk> wrote: >J. Hugh Sullivan wrote: >> On Wed, 13 Feb 2013 11:30:01 -0500, Denis Beauregard >> <denis.b-at-francogene.com@fr.invalid> wrote: >> >>> Personnally, I use LibreOffice so I can't comment about the >>> ease of use of the freewares ! I write what I need with PHP. >>> >>> >>> Denis >> >> Since you mentioned it... >> >> Can every document be saved as .doc and every spreadsheet as .xls? I >> know they CAN be - but by default? > >Yes. Default settings are configurable at Tools>Options>Load/Save>General > >Word options available are 6.0, 95, 97/2000/XP/2003 2003/XML 2007/2010 >XML in v 3.6.5. Excel are slightly different, 5.0 instead of 6.0 & also >template options. I'm not sure about the new v 4.0. The usual warnings >about non-native formats not necessarily representing what you see >probably apply but I'm not sure if that's a real problem any more. > >> Do the menu items mirror 2003 Office or 2007 that needed uBit to make >> the menu usable? > >AFAICS uBit is something that gets rid of the ribbon interface. They're >pre-ribbon style if that's what you're asking. It's so long since I >used MS Office I'm not sure how close they resemble Office otherwise but >you can customise tool bars & select icon size & style. > >-- >Ian I thank both of you for the responses. My grandson was just over to look at my non-boot desktop. He uses Open Office and recommends it. He is synced with any computer. Excel might be a bit sticky if one gets very sophisticated with it I think CNet recommends Libre. Hugh

On Thu, 14 Feb 2013 09:08:11 +1000, Henry Soszynski <royalty@iinet.com.au> wrote in soc.genealogy.computing: >On Tue, 12 Feb 2013 21:30:32 -0500, kraut / larry stark ><kraut3852@yahoo.com> wrote: > >>Suggestions for a good freeware genealogy program that is not too >>complicated. > >Brothers Keeper for windows, should fit the bill. Uncluttered, an easy >learning curve. BK is not FREE. It is a "try and pay" software, which doesn't fit the initial request. Denis -- Denis Beauregard - généalogiste émérite (FQSG) Les Français d'Amérique du Nord - www.francogene.com/genealogie--quebec/ French in North America before 1722 - www.francogene.com/quebec--genealogy/ Sur cédérom à 1780 - On CD-ROM to 1780

On Wed, 13 Feb 2013 22:22:52 GMT, Eagle@bellsouth.net (J. Hugh Sullivan) wrote in soc.genealogy.computing: >I thank both of you for the responses. My grandson was just over to >look at my non-boot desktop. He uses Open Office and recommends it. He >is synced with any computer. > >Excel might be a bit sticky if one gets very sophisticated with it > >I think CNet recommends Libre. Some netters thing that LO is updated more frequently and more effort is put in it compared to OOO since OOO/Sun was purchased by Oracle. I have OOO 2 and 3 but use LO on a daily basis. I open files from emails with OOO 3 but work my data files with LO. Denis -- Denis Beauregard - généalogiste émérite (FQSG) Les Français d'Amérique du Nord - www.francogene.com/genealogie--quebec/ French in North America before 1722 - www.francogene.com/quebec--genealogy/ Sur cédérom à 1780 - On CD-ROM to 1780

On Wed, 13 Feb 2013 19:31:57 +0000, Ian Goddard <goddai01@hotmail.co.uk> wrote in soc.genealogy.computing: >J. Hugh Sullivan wrote: >> On Wed, 13 Feb 2013 11:30:01 -0500, Denis Beauregard >> <denis.b-at-francogene.com@fr.invalid> wrote: >> >>> Personnally, I use LibreOffice so I can't comment about the >>> ease of use of the freewares ! I write what I need with PHP. >>> >>> >>> Denis >> >> Since you mentioned it... >> >> Can every document be saved as .doc and every spreadsheet as .xls? I >> know they CAN be - but by default? > >Yes. Default settings are configurable at Tools>Options>Load/Save>General > >Word options available are 6.0, 95, 97/2000/XP/2003 2003/XML 2007/2010 >XML in v 3.6.5. Excel are slightly different, 5.0 instead of 6.0 & also >template options. I'm not sure about the new v 4.0. The usual warnings >about non-native formats not necessarily representing what you see >probably apply but I'm not sure if that's a real problem any more. I know at least one problem. I print CD pockets with LO and I want to print the back and face parts vertically. It can print only on the wrong direction in English (in French, it is the opposite direction and it works correctly). Denis -- Denis Beauregard - généalogiste émérite (FQSG) Les Français d'Amérique du Nord - www.francogene.com/genealogie--quebec/ French in North America before 1722 - www.francogene.com/quebec--genealogy/ Sur cédérom à 1780 - On CD-ROM to 1780

Ian Goddard wrote: > singhals wrote: >> Ian Goddard wrote: >>> Dennis Lee Bieber wrote: >>>> On Tue, 12 Feb 2013 21:50:44 -0500, singhals<singhals@erols.com> >>>> declaimed the following in soc.genealogy.computing: >>>> >>>>> kraut / larry stark wrote: >>>>>> Suggestions for a good freeware genealogy program that is not too >>>>>> complicated. >>>>> >>>>> If you're looking for MAC and free, don't believe there is one. >>>>> >>>>> If you're looking for unix based one, there is one, I just >>>>> don't remember what it is; someone else will. >>>>> >>>> >>>> Gramps http://gramps-project.org/ >>>> >>>> Should be usable on anything that can run a reasonably up-to-date >>>> version of the Python language -- which includes Mac/Linux/Windows >>>> (heck, some subsets of Python run on cell phones) >>>> >>> >>> I rather fell out with Gramps after I upgraded to 3.3.1. Until that >>> point I hadn't realised that it didn't keep copies of media files in its >>> own database where, in my view, they should be kept. >> >> (G) Mostly to hold up the other end of the argument -- >> FTM kept media in its internal database and most folks hated not having >> access to the images from outside FTM. > > Easy. You only /copy/ them to the database. Don't delete the original. > Newbies don't think of /that/. They scan thru FTM and save where-ever it puts it. One copy, part of FTM. >> After the first few images were put in, most everyone discovered the >> database was growing exponentially, > > If that were really the case something would be wrong. It should just > grow linearly. You could be right, it's math after all, but 1 image tripled the file size on my test. 1, 300 dpi scan of a 2x3 B&W photo. >> and rather than reducing the number >> of images they reduced the quality. > > I suppose this comes back to me having been a database developer working > with an industrial-grade database engine. You want to keep bulky data? > You allocate lots of space for it. (G) But, you see, users don't think like developers. Users see "Store images internally" and they think COOL! They don't think, "How many images can I get on a 7G HD?" >> PAF5 like Gramps has you put the images into a separate directory; mine >> are under PAF/Data/[dbname_img] and I finally got clever enough to put >> the path into the NOTES >> as a hedge against the next head-crash. > > AFAICS what Gramps was originally doing was to simply note the path& > filename of what you supplied. Only at export time did it take a copy. > That would mean if you reorganised what you though was an > outside-Gramps system it wouldn't have been able to find anything. > > BTW I installed the current version onto another Linux instance on a VM > & tried running the import again. It still has the same default > locations but will allow a merge. > > But I'd forgotten another of its little egregious features which is > still there. Each database has a name, e.g. 1881Census. But by the > time you've exported& reimported it's something like Family Tree 01 so > you have to go through the lot renaming them. Ooops? Can't you change the code for the default to echo the file-name? Cheryl

J. Hugh Sullivan wrote: > On Wed, 13 Feb 2013 11:30:01 -0500, Denis Beauregard > <denis.b-at-francogene.com@fr.invalid> wrote: > >> Personnally, I use LibreOffice so I can't comment about the >> ease of use of the freewares ! I write what I need with PHP. >> >> >> Denis > > Since you mentioned it... > > Can every document be saved as .doc and every spreadsheet as .xls? I > know they CAN be - but by default? Yes. Default settings are configurable at Tools>Options>Load/Save>General Word options available are 6.0, 95, 97/2000/XP/2003 2003/XML 2007/2010 XML in v 3.6.5. Excel are slightly different, 5.0 instead of 6.0 & also template options. I'm not sure about the new v 4.0. The usual warnings about non-native formats not necessarily representing what you see probably apply but I'm not sure if that's a real problem any more. > Do the menu items mirror 2003 Office or 2007 that needed uBit to make > the menu usable? AFAICS uBit is something that gets rid of the ribbon interface. They're pre-ribbon style if that's what you're asking. It's so long since I used MS Office I'm not sure how close they resemble Office otherwise but you can customise tool bars & select icon size & style. -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk

On Wed, 13 Feb 2013 11:30:01 -0500, Denis Beauregard <denis.b-at-francogene.com@fr.invalid> wrote: >Personnally, I use LibreOffice so I can't comment about the >ease of use of the freewares ! I write what I need with PHP. > > >Denis Since you mentioned it... Can every document be saved as .doc and every spreadsheet as .xls? I know they CAN be - but by default? Do the menu items mirror 2003 Office or 2007 that needed uBit to make the menu usable? Hugh

On Wed, 13 Feb 2013 16:48:48 -0500, singhals <singhals@erols.com> wrote: >Denis Beauregard wrote: >> Le Tue, 12 Feb 2013 21:50:44 -0500, singhals<singhals@erols.com> >> écrivait dans soc.genealogy.computing: >> > >>> Legacy is a bit more complex and a lot prettier to look at. >>> It has a free version. >> >> I would prefer Legacy over PAF because PAF is outdated. The >> last release may be more than 10 years ago (or little changes >> after that). Also, you have to be sure PAF will work on Win 7 >> or 8, a problem with old softwares. > >Good grief, Denis! You'n'I are more'n 10 years old too, and >I'd sooner my family didn't abandon me for a newer edition! ;) > >Cheryl LOL... In my view the only problem with PAF is that later editions never lived up to PAF 2.3

The difference is that a 10 year person can learn new things and adjust their 'programming' - a 10 year old computer program can't. ;) -----Original Message----- From: singhals <singhals@erols.com> To: gencmp <gencmp@rootsweb.com> Sent: Wed, Feb 13, 2013 3:48 pm Subject: Re: Suggestions for a good freeware genealogy program that is not too complicated. Denis Beauregard wrote: > Le Tue, 12 Feb 2013 21:50:44 -0500, singhals<singhals@erols.com> > écrivait dans soc.genealogy.computing: > >> Legacy is a bit more complex and a lot prettier to look at. >> It has a free version. > > I would prefer Legacy over PAF because PAF is outdated. The > last release may be more than 10 years ago (or little changes > after that). Also, you have to be sure PAF will work on Win 7 > or 8, a problem with old softwares. Good grief, Denis! You'n'I are more'n 10 years old too, and I'd sooner my family didn't abandon me for a newer edition! ;) Cheryl ------------------------------- To unsubscribe from the list, please send an email to GENCMP-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

Denis Beauregard wrote: > Le Tue, 12 Feb 2013 21:50:44 -0500, singhals<singhals@erols.com> > écrivait dans soc.genealogy.computing: > >> Legacy is a bit more complex and a lot prettier to look at. >> It has a free version. > > I would prefer Legacy over PAF because PAF is outdated. The > last release may be more than 10 years ago (or little changes > after that). Also, you have to be sure PAF will work on Win 7 > or 8, a problem with old softwares. Good grief, Denis! You'n'I are more'n 10 years old too, and I'd sooner my family didn't abandon me for a newer edition! ;) Cheryl