Everything in your posting is Greek to me. What are you talking about? I am not a programmer.
CE From: [email protected] Date: Tue, 30 Apr 2013 11:32:55 -0700 Subject: Re: [LegacyUG] Re: Sorting Events To: [email protected] CE, Legacy has always had a 'sort date' field. It is hidden from view but derived from the data in the date field you see and can edit. The following is an old copy (ver 6) of DATES, I doubt anything has changed; -------------------------------------------------------------------------------------- 'Format of StoreDate 'pbddmmyyyyddmmyyyy 'p = prefix ' If the Len(StoreDate) > 1 ' :=bad date, 0=normal,1=abt, 2=cir, 3=bef, 4=aft, 5=bet, 6=bc, 7=ad, 8=WFT Est ' g=est, h=cal, F=from, T=to, M=to between dates, s=banns, t=lic ' b=british quarter dates (Mar Q yyyy, Jun Q yyyy, Sep Q yyyy, Dec Q yyyy) ' <=date displayed with brackets around it...an estimated date <12 Dec 1800> ' [=a private date used only for sorting purposes [[12 Dec 1800]] ' ?=a date with a question mark after it 12 Dec 1800 ? ' |=two dates with "or" between them "12 Dec 1888 or 13 Nov 1889" or "17 Feb 1718 or 1719" ' ' If the Len(StoreDate) = 1 ' ?=unk, a=dead, b=deceased, c=child, d=infant, e=stillborn, f=young, ' g=Submitted, h=Cleared, i=uncleared, j=completed, k=cancelled, l=bic, m=dns, ' n=dns/can, o=see notes, p=pre-1970, q=done, r=private, s=banns, t=lic, ' u=not married, v=never married, ?=unknown 'b = bc flag 'Also, if the date is partially recognizable so that we can get a sort date out of it, we put the ' pieces we recognize into the ddmmyyyyddmmyyyy slots, put a colon at the beginning prefix position ' and then put a backslash (\) in the 19th position, followed by the date entered by the user. ' So, if a date starts with a colon but has \ in position 19 then display the Mid$(TheDate, 20) ' "Close to 31 Jan 1961" becomes :03101196100000000\Close to 31 Jan 1961 ' This way we can act like the date is OK and display it as the user entered it. ******************************************** *************** Sort Dates ***************** ******************************************** 'Sort Date (long int) Used to display sorted list by date if date is blank then -99999999 (sorts before any other date) otherwise the number is made up of the yyyymmdd digits (25 Dec 2000 would be 20001225) BC are negative, AD are positive (1 Jan 400 BC would be -40000101) If no date, the number is -99999999. If there is a year but no month and no day then If there is a "Before" modifier then the mmdd is set to "0101" (Bef 1834 would be 18340101) ElseIf there is an "After" modifier then the mmdd is set to "1231" (Aft 1834 would be 18341231) Else mmdd is set to "0000" for no month and no day (1834 would be 18340000) End If End If If no day then If there is a "Before" modifier then the dd is set to "01" (Bef Dec 1678 would be 16781201) ElseIf there is an "After" modifier then the dd is set to the last day of the month (Aft Feb 1678 would be 16780228) Else dd is set to "00" no day (Dec 1678 would be 16781200) End If -------------------------------------------------------------------- hope that helps Jay On Tue, Apr 30, 2013 at 10:23 AM, CE WOOD <[email protected]> wrote: A sort date would be a wonderful addition to the options for sorting events. There are many people for whom I must move each event around to get them appearing in a coherent manner. When you sort alphabetically by event, they are not in date order; when you sort by date, events are not in alphabetical order. Since Legacy is Access based, it should be possible to add a sort date column or be able to have secondary sort parameters. It is incredibly frustrating to add a new event to those whom I have so carefully sorted, since I can never use the simplistic sorting that is available. Some of these people have at least one hundred events! CE Date: Tue, 30 Apr 2013 07:24:20 -0400 Subject: Re: [LegacyUG] Re: Chart showing occupation From: [email protected] To: [email protected] Larry, What you are describing is already available in RootsMagic and The Master Genealogist. It is called a sort date. This is exactly why I have said on more than one occasion that Legacy is outdated/behind the times. Legacy used to be an excellent program. Unfortunately, Millennia doesn't seem to be the least bit interested in staying on top. They are falling further and further behind their competition. Ron Bernier,Woonsocket, RI On Tuesday, April 30, 2013, Larry wrote: Jenny, 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 planning to offer this as a suggestion to Millennia. What are your thoughts on this idea? Larry Lee -- Ron Bernier Woonsocket, RI 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 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
