On a cost/benefit analysis, programmers cost more than data-entry. Even more so when the data-entry level is volunteer. Why pay $40 a hour figure out how to save a volunteer a few minutes? :^)
Cheryl-the-cynical JV Leavitt wrote: > Yes, thank you, that is right. It wasn't always necessary to do a > work-around process in order make up for a deficiency in this particular > software need. Moreover, it takes more time for us to do it this way. > In other words, our time is wasted because the programmers don't > understand the necessity, or else, maybe more likely, they are > determined to make sure it takes more time for us to do everything. > > Joseph Leavitt > > > On 8/11/2014 8:44 AM, Carl Cox wrote: >> <<When you are working in FT and a parent couple >> exists there, and you try to add one of the parents to a child, the >> program will make a new parent relationship (without asking) that >> doesn't include the other parent of the child!>> >> >> In both FT and Legacy, you put the parents where they belong, and add (or >> link) the children to that couple. Trying to add parents to a child can >> cause problems for both programs. Also, I always add the child to the >> correct parents before unlinking from the wrong place. That way they don't >> get lost. >> >> Carl Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
