I'm almost ignorant on this subject, but how difficult would it be for those who write the code for RootsMagic to make the program sort by EVENT, i.e., Birth, Christening, Marriage, Death, Burial, etc., regardless of the date? FTM does that automatically, Birth comes before Marriage, Marriage comes before Death, Death comes before Burial, etc. Is it so difficult to sort by logical Events? Doesn't seem to be an insurmountable problem, just takes common sense. If Birth, Death, and Burial all happen in the same year, why can't RM automatically align the events to show a logical progression? Sarge Germanna Database at Ancestry: http://trees.ancestry.com/tree/28427876/family My Germanna Database at Rootsweb: http://wc.rootsweb.ancestry.com/cgi-bin/igm.cgi?db=germanna My Germanna Website at Rootsweb: http://homepages.rootsweb.ancestry.com/~george/index.html

I just don't see this being the big issue that people are making it.  I just have never found it to be a problem so I wrote a small program to find where I had the same date for birth and baptism, birth and death, or death and burial;  It turns out to be in less than one half of one percent of the total number of fact entries in my database.  On those rare occasions when they might be the same I use the sort date or the more common case for me is where I pick up the Death Date from a tombstone I enter the death date as that on the tombstone and the burial date as being AFT the death date.   Doing it at the time of data entry takes no time at all.  I would rather see Bruce continue to use his time to provide us with new capabilities like he has been doing than "fix" a problem that is easily handled by the program as it now stands.  ----- Original Message ---- From: George W. Durman <GermannaResearch@comcast.net> To: rootsmagic-users@rootsweb.com Sent: Thu, December 27, 2012 12:00:57 AM Subject: Re: [RMagic] RootsMagic 6 - sorting of birth, death and burial events when all occur in the same year I'm almost ignorant on this subject, but how difficult would it be for those who write the code for RootsMagic to make the program sort by EVENT, i.e., Birth, Christening, Marriage, Death, Burial, etc., regardless of the date? FTM does that automatically, Birth comes before Marriage, Marriage comes before Death, Death comes before Burial, etc. Is it so difficult to sort by logical Events?  Doesn't seem to be an insurmountable problem, just takes common sense. If Birth, Death, and Burial all happen in the same year, why can't RM automatically align the events to show a logical progression? Sarge Germanna Database at Ancestry: http://trees.ancestry.com/tree/28427876/family My Germanna Database at Rootsweb: http://wc.rootsweb.ancestry.com/cgi-bin/igm.cgi?db=germanna My Germanna Website at Rootsweb: http://homepages.rootsweb.ancestry.com/~george/index.html =================================== RM list Archives: http://archiver.rootsweb.com/th/index/ROOTSMAGIC-USERS/ http://archiver.rootsweb.com/cgi-bin/search?path=ROOTSMAGIC-USERS WISH LIST: http://www.rootsmagic.com/forums/  BLOG: http://blog.rootsmagic.com/ ------------------------------- To unsubscribe from the list, please send an email to ROOTSMAGIC-USERS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

> I'm almost ignorant on this subject, but how difficult would it be for > those > who write the code for RootsMagic to make the program sort by EVENT, > i.e., Birth, Christening, Marriage, Death, Burial, etc., regardless of the > date? The "regardless of date" is the part that many users don't want. It's one thing for a birth in 1900 to come before a death in 1900. That's ok, and it's way better than a death in 1900 coming before a birth in 1900. It's another thing altogether for a birth in 1901 to come before a death in 1900. The latter case is an error that the user should deal with. The program should not move a birth in 1901 in front of death in 1900, or at least a lot of users don't think it should. Jerry