Hi Guys Long time since I posted anything. I stuck with V16 until last year. Since then I have TRYING to get 2014 up and running. My db has 130,000+ and almost 500k Facts. the max for V16. Initially I started on the older (new) versions and gave up - but I can see there is no way ahead without biting the bullet. Since I got back from my last cruise - London - Fremantle on Dec 12, I have spent every waking moment trying to work thru the "Places". I am starting to get the hang of it and have got sidetracked by trying to find all the cousins and rellies KIA in WW1. Not an easy job. Why they had to change to way the system works is beyond me. V16 did not "hang" and require compaction like this does. I see people complaining about it regularly. And you guys claim it is "more stable". I think the horse has bolted. Clearly there are advantages in using 2014, however I keep seeing MY work (and MY errors) replicated all over searches and real crumby research on trees submitted. I only look at historical records. I don't think we have much option but to switch - but I still backup and keep my old V16 up to date - but have to delete people from time to time to keep size down, Those are my opinions, Clem in Perth, Western Austrlia

> My db has 130,000+ and almost 500k Facts. the max for V16. I never had 500k facts, but 130K people is no where NEAR a limit in FTM 16. I have run trees provided by other people with 800,000 people and FTM 16 chugs along just fine. My current file is in FTM 2014 with 143,XXX people and it works well with a 64-bit operating system. > Since I got back from my last cruise - London - Fremantle on Dec 12, I > have spent every waking moment trying to work thru the "Places". There had been instructions out almost a decade ago on how to prepare one's database for the transition, but I didn't fix my file either. I spent 12 hours a day for many weeks fixing things using the Place Name Authority (PNA) and am VERY happy I did so. Besides the obvious corrections, I found multiple misspellings I wouldn't have caught otherwise. There are several trains of thought on how to fix one's places, so it you want suggestions, just ask others. I try the KISS method personally. John Okerson Lakeland, Shelby County, Tennessee, USA

Hi CJ & Julia from one of the 'gals' on this list. Allie -----Original Message----- From: CJ & Dr Julia Edwards via Sent: Saturday, February 21, 2015 8:06 AM To: ftm-tech@rootsweb.com Subject: [FTM-TECH] The Not So Great Debate V16 v 2014. Hi Guys Long time since I posted anything. I stuck with V16 until last year. Since then I have TRYING to get 2014 up and running. My db has 130,000+ and almost 500k Facts. the max for V16. Initially I started on the older (new) versions and gave up - but I can see there is no way ahead without biting the bullet. Since I got back from my last cruise - London - Fremantle on Dec 12, I have spent every waking moment trying to work thru the "Places". I am starting to get the hang of it and have got sidetracked by trying to find all the cousins and rellies KIA in WW1. Not an easy job. Why they had to change to way the system works is beyond me. V16 did not "hang" and require compaction like this does. I see people complaining about it regularly. And you guys claim it is "more stable". I think the horse has bolted. Clearly there are advantages in using 2014, however I keep seeing MY work (and MY errors) replicated all over searches and real crumby research on trees submitted. I only look at historical records. I don't think we have much option but to switch - but I still backup and keep my old V16 up to date - but have to delete people from time to time to keep size down, Those are my opinions, Clem in Perth, Western Austrlia ********************************** List information page http://lists.rootsweb.com/index/other/Software/FTM-TECH.html ------------------------------- To unsubscribe from the list, please send an email to FTM-TECH-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message