On 30/04/2013 12:08, Larry wrote: > I raised that same issue. I have recently been thinking about this > issue of showing events in reports. My thought so far is that events > do have dates associated with them, although we may not know the > date(s). For practical sorting reasons I believe it would be > necessary to have what I term a "Pseudo Date". This would allow an > event to be displayed in a timeline in a "user assigned" or > approximated position rather than at the top of a list by default. > Here is a simplistic example to illustrate this. If I were to use a > Burial Event to show the cemetary information, I most likely don't > know the date. To prevent this from appearing at the top of a > chronological listing, ie., before they were born, which is obviously > absurd, I would use a Pseudo Date following the Death Date to place > it in correct sequence. This Pseudo Date could be set to invisible so > it wouldn't show on a report giving the false impression that it is a > known date. A Pseudo Date could also be useful in sorting children. I > know Mary to be the third child but have no Birth Date, for example.
I am happy to use "About", "Before" or "After" where I don't know an exact date but feel one is necessary/useful. I think any of these is sufficient to show that the exact date is not known. -- 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
