Yes, So, I went thru and deleted all those "General Notes". Now I cannot open the database again. Says it cannot lock the file. So I moved the file from my Google Drive folder to the recommended folder and it seems to be opening oK now (today). Maybe it doesn't like a cloud storage for the active family file (.fdb) so I guess I'll just put my zip backups in the cloud and let the family file stay on my PC.
*Marilyn* On Sat, May 2, 2015 at 3:45 PM, Sherry/Support <[email protected]> wrote: > Hard to say. This might be something the techs need to look at - the > original file as well as the gedcom. > > The error message said "can't open database" but you need to have it > open to create the gedcom! Did you get this while you were working in > the file? It generally means the Family File is corrupted and > hopefully the gedcom will restore it. > > > Sincerely, > Sherry > Technical Support > Legacy Family Tree > > > On Sat, May 2, 2015 at 2:03 PM, Marilyn Clark <[email protected]> > wrote: > > OK, thanks Sherry. I wonder why, since I used Legacy to create the > GEDCOM, > > it would export "using unrecognized non-standard gedcom tags" ?? > > > > I'll just go thru and check each of the individuals listed in the error > log > > and make sure they are OK. While I have them up onscreen I'll delete the > > notes. > > > > Marilyn > > > > On Sat, May 2, 2015 at 11:58 AM, Sherry/Support > > <[email protected]> wrote: > >> > >> 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: > >> > > > > > > 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
