I would vote for the same sex, relationship provision. Just to include everyone in one's family tree.
On Thu, Dec 26, 2013 at 12:01 PM, grayscot2 <[email protected]> wrote: > > I'd like to up the count for including provisions for same sex > marriage, "significant others", poly-amorous, etc. > > But also, switching to a different underlying database program. > Anything so fragile as to need constant check/repairs is far too fragile. > I've used Dbase3, Visual Fox Pro and a number of free-form databases that > never required this. Zoot for instance is a free-form database PIM that is > arguably just as complex or moreso than Legacy, but I've never had to check > or repair its many separate smart databases, and in 20 years, through disk > failures, crashes, and power failures/surges that burnt out everything > else, cloud sync failures, have never lost an item. > > So if you have to re-do the program anyway--and with Utah going > same-sex marriage, you will surely have to--get a stabler database/file > system. > > Pres > ---------------------------------------------------------- > Prescott Smith [email protected] > > ============================================================================ > From: Sherry/Support [[email protected]] > Sent: Thursday, 26 December, 2013 12:22 PM > To: [email protected] > 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 > > On Thu, Dec 26, 2013 at 10:16 AM, singhals <[email protected]> wrote: > > Most two-sex marriages these days aren't "life-long" either, > > though. > > > > My not needing the ability to add same-sex relationships > > doesn't mean someone else won't need it, and I can always > > not-use it if it's there. > > > > If someone's keeping count, here's a "it might be a nice > > option" vote. > > > > Cheryl > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > 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 > > --- > This email is free from viruses and malware because avast! Antivirus > protection is active. > http://www.avast.com > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > 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/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ 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
