On 30/04/2013 12:55, Ron Bernier wrote: > The issue is that an occupation doesn't necessarily need a date. If > Legacy used sort dates, this would allow you to put (sort) the > occupation (or any event for that matter) in the proper sequence without > having to show a guesstimated date - sort dates only show in your data, > not in your reports. >
There are two ways of looking at this. "Joe Bloggs was a a Carpenter" doesn't need a date if you are fairly sure that Joe was a carpenter for most/all of his working life. "On 30 April 2013 Joe Bloggs occupation was stated to be Carpenter" is not the same thing at all. If you don't have a date and just know that Joe was a carpenter, whereabouts in a list of Events/Fact do you want that one to sort? I am happy for it to be at the start. Mostly where I se an estimated date is because I want some sort of date to appear. -- Jenny M Benson 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
