I've been following this thread with some interest, although I have none of those relationships in my personal records. I think Bill states an obvious and simple solution to this. I've been pondering the ramifications of such a change in the database from a totally non-programming knowledge basis. Even charting where the color coding can be based on sex. I feel that the simple solutions without restructuring everything in the programs, would be the best for everyone. Every time you make a major change, something else suffers as we've seen during the recent update of Legacy Family Tree. Any time we can make a simple work around, it will be best. I would be interested in hearing other 'work arounds'
We need to stop this thread though because it is going to become 'political' pretty soon. And this is not just a Legacy Family Tree issue so no pointing fingers at them either. We all share an interest in tracing our family history and discovering our ancestry; this is no place for current event discussions. I'm quite happy to have the holidays over, and be happily unemployed for a little while, so I can get back into MY family history work and finally learn the ins and outs of our new Legacy 8 upgrade! I will be posting frequently I'm sure so thank you in advance to all of you who are so kind to give advise. Kathy On Thu, Dec 26, 2013 at 12:15 PM, William Boswell <whbosw...@gmail.com>wrote: > I think the easiest solution is to just add the same-sex partner as either > a wife or husband whether their sex matches that position or not. The > marriage options allow adding whatever you want under "Master Marriage > Status List" and you can also put a note that both individuals are either > male or female. > > Bill Boswell > > -----Original Message----- > From: Sherry/Support [mailto:she...@legacyfamilytree.com] > Sent: Thursday, December 26, 2013 1:22 PM > To: LegacyUserGroup@LegacyUsers.com > Subject: Re: [LegacyUG] Same Sex Partnerships/Marriages > > We are "keeping count" somewhat, but as Leonard wrote quoting Ken, it's a > major ripping apart of the basic design of Legacy and would be very time > consuming for the programmers. Not only would they have to restructure > Legacy, they would also have to re-code all the other options based on the > restructuring - not to mention the trickle-down for all the add-on programs. > > > Sincerely, > Sherry > Technical Support > Legacy Family Tree > > > > > > 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 > > > 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
