I am far from an expert, but maybe I can explain one of the major problems with the technology behind nFS vs. Family Tree as I understand it. nFS is sort of a resource hog. Both programs use the same database, but in order to get the data to your PC there are differences. Try this analogy of the technology: nFS is like trying to get 100,000 cars down a two lane road fast. FamilyTree is like sending 100 cars down the same two lane road. nFS uses a great deal more resources to get the info from the database to your PC than Family Tree does. Also, as was explained to me, one of the things they are trying to do is take certain parts of Family Tree that are working much better than in nFS, and integrate these parts into nFS. So over time they will be blended together with the best parts of each. All of these things are just a sign of the times...technology times. The one thing we have to do is have patience and understanding with them. I know the older I get I have a choice to make... either get frustrated or deal with it and take the changes as challenges I can master... or at least give it a good shot :) SueM Sahara346@aol.com wrote: > What was the point of developing NFS, then as people get comfortable with > it, switching again? Why not just fix the glitches in the first program. > I don't find FT nearly as easy to navigate around in, and so don't go to it > very often. > > Karen > > >

Yes, I agree. The way I look at it is in NFS all of the data is in one huge folder and open all the time. It will not be possible to bring on the public and deal with the amount of duplications that exist within a reasonable amount of server time. FS Family Tree has each individual in their own folder so that data and bytes are only used when the folder is open. Someone who is more computer tech savvy than me may not agree with this but the above is how I think about it. Nancy Scott Cincinnati, Ohio -----Original Message----- From: lds-ward-consultant-bounces@rootsweb.com [mailto:lds-ward-consultant-bounces@rootsweb.com] On Behalf Of Sue Maxwell Sent: Friday, June 19, 2009 11:33 AM To: lds-ward-consultant@rootsweb.com Subject: Re: [LDS-WC] NFS in Utah I am far from an expert, but maybe I can explain one of the major problems with the technology behind nFS vs. Family Tree as I understand it. nFS is sort of a resource hog. Both programs use the same database, but in order to get the data to your PC there are differences. Try this analogy of the technology: nFS is like trying to get 100,000 cars down a two lane road fast. FamilyTree is like sending 100 cars down the same two lane road. nFS uses a great deal more resources to get the info from the database to your PC than Family Tree does. Also, as was explained to me, one of the things they are trying to do is take certain parts of Family Tree that are working much better than in nFS, and integrate these parts into nFS. So over time they will be blended together with the best parts of each. All of these things are just a sign of the times...technology times. The one thing we have to do is have patience and understanding with them. I know the older I get I have a choice to make... either get frustrated or deal with it and take the changes as challenges I can master... or at least give it a good shot :) SueM Sahara346@aol.com wrote: > What was the point of developing NFS, then as people get comfortable with > it, switching again? Why not just fix the glitches in the first program. > I don't find FT nearly as easy to navigate around in, and so don't go to it > very often. > > Karen > > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM ------------------------------- To unsubscribe from the list, please send an email to LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message