Ron,
. You could also try exporting your records into a new Legacy family file:
Click on File > Export > Export to a new Legacy Family File.
Give your new family file a name and click Save and the Legacy Export
screen will open.
Click the Privacy Options button to open the Privacy Options screen.
In the lower half of the screen, under Override Private Settings, click the
Check All button and then click Save.
In the Legacy Export screen check mark Include general To-Do items and then
click Start the Export.
If the AutoSource Reminder screen opens, click the Don't Assign a Source
button.
The export will begin. When it's complete click OK.
When asked "Would you like to open the file you just export to?" click the
Yes button.
Use the new family file and delete the old one when you are satisfied the
Potential Problems date error is fixed.
. If the Legacy export doesn't fix the problem, try exporting your records to a
GEDCOM file and then import the GEDCOM back into Legacy. If you use the
SourceWriter to create sources, please be aware that your SourceWriter sources
will be converted to the Basic Source system so do this step as a last resort.
1) Click on File > Export > GEDCOM File. The GEDCOM Export window appears.
2) In the Produce file for: box, select Legacy (this is the default. It should
already be selected.).
3) Click the Privacy Options button to open the Privacy Options screen.
4) In the lower half of the screen, under Override Private Settings, click the
Check All button and then click Save.
5) When you are ready to export, click the Select File Name and START EXPORT
button. Legacy prompts you for a file name and location, and then creates the
GEDCOM file for you. Remember the location on your hard drive where you save
the GEDCOM file. You will need to be able to locate it in order to import into
the other Legacy program.
When the export is finished, import it back into Legacy as a new family file.
Click on File and select Import > GEDCOM File and follow the prompts.
. If all else fails, restore your family file from your backup copy.
Jim
Legacy Family Tree
Technical Support
-------- Original Message --------
> From: "Goodwin Genealogy" <[email protected]>
> Sent: Friday, July 17, 2015 7:54 PM
> To: [email protected]
> Subject: RE: [LegacyUG] Potential Problem with dates
>
> Thanks for the suggestions Jim.
> I have tried the check and repair several times, but it didn't fix the
> problems.
> So I will now give your second suggestion a try.
> Thanks
> Ron
>
> -----Original Message-----
> From: Jim Terry/Support [mailto:[email protected]]
> Sent: Friday, July 17, 2015 16:10
> To: [email protected]
> Subject: re: [LegacyUG] Potential Problem with dates
>
> Ron,
>
> Sometimes i have had a record for a person that has unusual problems like
> you are reporting. I have fixed the problem with check and repair. See
> http://support.legacyfamilytree.com/article/AA-00749 for the steps.
>
> On extremely rare occasions the only way I could fix a problematic record
> is to delete it and then create a new record for the person. I recommend
> print an Individual Report for the person before you begin.
>
> Jim
> Legacy Family Tree
> Technical Support
>
>
>
>
> -------- Original Message --------
> > From: "Goodwin Genealogy" <[email protected]>
> > Sent: Friday, July 17, 2015 10:41 AM
> > To: [email protected]
> > Subject: [LegacyUG] Potential Problem with dates
> >
> > I am experiencing a problem with the Potential Problem reports, for some
> > reason it is not reading the entered dates properly.
> >
> >
> >
> > It is reporting a problem where it says that the entered date is 1774
> where
> > the date that I have entered is 1874.
> >
> > I have run the "check/repair" several times and have deleted and
> reentered
> > the 1874 date several times but the problem remains.
> >
> >
> >
> > I have this same problem with other entries but only with about 5% of my
> > entries while the others are fine.
> >
> > I have checked and reset the Potential Problems "Gaps" menu but nothing
> > helps.
> >
> > I have also re-downloaded Legacy .501 with no change.
> >
> >
> >
> > Any suggestions?
> >
> >
> >
> > Ron Goodwin
> >
> > Ottawa, Ontario
>
>
>
>
> 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://support.legacyfamilytree.com
>
> 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://support.legacyfamilytree.com
>
> 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://support.legacyfamilytree.com
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
