That just means that the gedcom you imported had a bunch of information exported by the program using unrecognized non-standard gedcom tags - Legacy didn't know where to put them so to prevent loss of data, Legacy puts them in the Notes.
The data was placed in the Notes for the individuals listed and you'll need to decide what to do with the information. Sincerely, Sherry Technical Support Legacy Family Tree On Sat, May 2, 2015 at 10:30 AM, Marilyn Clark <[email protected]> wrote: > I had some problems with my version 8 deluxe database (Version 8.0.0.459 > build date 5 Dec 2014) this week (error 3049 'Cannot open database") and > followed directions for exporting to a GEDCOM and importing that GED into a > new Legacy .fdb. During this process, it generated an error report, which I > saved. Then I did a check file/maintenance on the new database and it seems > OK. > > I do not know what to do with this error report, it's quite lengthy and > points to my most recent changes to the .fdb file before having to create > this GEDCOM etc. > > Here is a section of the report: > > Error report for: C:\Users\Marilyn\Desktop\Replogle-fix.ged. > > Main Record: 0 @I1536@ INDI > Sub Section: 1 NAME James L /GLENN/ > * Unrecog. Line for an Individual Record: 3 _SOUR 1 > Placed in Note - James L GLENN: NAME: _SOUR 1 > ---------------------------------------- > Main Record: 0 @I1536@ INDI > Sub Section: 1 NAME James L /GLENN/ > * Unrecog. Line for an Individual Record: 3 _INFO 1 > Placed in Note - James L GLENN: NAME: _INFO 1 > ---------------------------------------- > Main Record: 0 @I1536@ INDI > Sub Section: 1 NAME James L /GLENN/ > * Unrecog. Line for an Individual Record: 3 _EVID 1 > Placed in Note - James L GLENN: NAME: _EVID 1 > ---------------------------------------- > Main Record: 0 @I1536@ INDI > Sub Section: 1 BIRT > * Unrecog. Line for an Individual Record: 3 _SOUR 1 > Placed in Note - James L GLENN: BIRT: _SOUR 1 > ---------------------------------------- > Main Record: 0 @I1536@ INDI > Sub Section: 1 BIRT > * Unrecog. Line for an Individual Record: 3 _INFO 1 > Placed in Note - James L GLENN: BIRT: _INFO 1 > ---------------------------------------- > Main Record: 0 @I1536@ INDI > Sub Section: 1 BIRT > * Unrecog. Line for an Individual Record: 3 _EVID 1 > Placed in Note - James L GLENN: BIRT: _EVID 1 > ---------------------------------------- > Main Record: 0 @I1536@ INDI > Sub Section: 1 DEAT > * Unrecog. Line for an Individual Record: 3 _SOUR 1 > Placed in Note - James L GLENN: DEAT: _SOUR 1 > ---------------------------------------- (and so on, for a total of 20 > individuals)-------------- > > You get the idea. So now I have this type of information in the notes > section of all these flagged individuals: > > NAME: _SOUR 1 > NAME: _INFO 1 > NAME: _EVID 1 > BIRT: _SOUR 1 > BIRT: _INFO 1 > BIRT: _EVID 1 > DEAT: _SOUR 1 > DEAT: _INFO 1 > DEAT: _EVID 1 > EVEN: _SOUR 1 > EVEN: _INFO 1 > EVEN: _EVID 1 > > BTW, This particular record, for "James L GLENN" appears to be OK. > > My question: What should I be doing to make certain all is OK with my > newly-generated .fdb file? What do I do with this error log? > > Other info FYI: The problems originally occurred on Version 8.0.0.459 build > date 5 Dec 2014. After exporting & importing the GEDCOM, I discovered that > my Index view did not display "Married Names" as it had before. I researched > this in the UserGroup archives and I think I have fixed that problem. But in > the meantime I updated the Legacy program to its newest version, hoping that > it was due to a bug that had been fixed. So currently I have running Version > 8.0.0.473 Build date 26 Feb 2015, Deluxe. > > > 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://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
