Thanks Robert! I knew something (very little) about the calendar change but didn't think it was critical to my research (yet.) Nice to know I can put it back later on if I need to.
Marilyn --- On Fri, 1/1/10, Robert Carneal USA <[email protected]> wrote: > From: Robert Carneal USA <[email protected]> > Subject: Re: [LegacyUG] Date with a slash cannot be corrected > To: [email protected] > Date: Friday, January 1, 2010, 5:29 PM > I suspect you have double dating > activated. It is desireable to some > of us, not quite so much on others. (I use double > dating.) Quoting > from Legacy Help: > > [Direct copy from Legacy Help, Copyright Millennia] > Legacy supports the practice of double dating to handle > the time period between the changeover from the Julian > to the Gregorian calendar. To turn this > feature on, click > Customize on the Options menu, and then click the Dates > tab. With this feature selected, entering a date that > falls > between January 1, 1583 and March 24, 1752 (or any > cutoff date you specify) displays it as a double date. > You can specifically enter the double date, such as > Feb. 16, 1723/24 or Feb 16 1723/1724, in which > case Legacy displays it as Feb 16, 1723/24. If you > don't include the second year, Legacy accepts the > year you entered as the second year. Jan 16, 1652 > becomes Jan 16, 1651/52. > [End Copy from Help] > > Does this help? > > Happy New Year, > > Robert > > > At 2010-01-01 06:18 PM, you wrote: > >The strangest thing is happening to me. I have a birth > date that > >appears as 30 Jan 1745/46. I want to make it 30 > Jan 1746 but the > >program will not accept it. > > > >I have typed over it (reverts to 30 Jan 1745/46), > deleted the entire > >date (it deleted OK), returned and made it just Jan > 1746 (reverts to > >Jan 1745/46), made it just 1746 (OK), then added Jan in > front of > >1746 (reverts to Jan 1745/46), Put the year first > (reverts to 30 Jan > >1745/46)...lots of other things to goose the date but > if I even put > >1740 in, it makes it 30 Jan 1739/40 instead. All this > happens when I > >click "Save" from the Individual's information screen. > > > >Backed up and closed Legacy, restarted the program and > the same > >things happen. What in the world is wrong?? > > > >Another thing...this person came to my Legacy file from > a GEDCOM > >from a freeware program over a year ago. It's my 4th > GGrandfather so > >I can't just ignore it. The date was 30 Jan 1746 on the > other > >database, so I never typed it in that way, originally! > I ran a > >Potential Problems report just now and the date doesn't > come up in error. > > > >Marilyn > > > > 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 > > 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
