Syble, There have been a number of valid suggestions given elsewhere about transferring the data from V7.5 to V8.0.
Personally, I use "File>Save As" to save the .fdb file I intend to move. V8.0 has by default the Legacy data files saved in ~Yr Name>My Documents>Legacy Family Tree>Data. Move the new .fdb file which you created to that folder, and in V8.0 simply use File>Open File then "Select using Windows Dialog" and go to that folder. Ron Ferguson http://www.fergys.co.uk/ From: Syble Glasscock Sent: Saturday, November 30, 2013 12:35 AM To: [email protected] Subject: Re: [LegacyUG] GEDCOM Re: Ron's comments: " Legacy cannot satisfactorily import its own GEDCOM." I'm not one to be among the first to download and update, nor to buy an update due to the many problems that I've read about since I began using Legacy years ago starting with version 5 or 6. I'm not as computer literate as some, and my main concern is to have Legacy operating properly, I can wait on all the "bells & whistles". My horror is to loose all these years of work just to get a few more options. I was very disappointed when I read the about updates for version 8, some sound okay, but when I do buy v.8, I had every intention of keeping Version 7.5, until I felt comfortable with v.8, now I read that I should not import my Legacy 7.5 as a Gedcom to v. 8, so it's there a simple process, without overriding v.7.5 WHY release something that seemingly has so many problems? Thanks, Syble On Friday, November 29, 2013 1:57 PM, Ron Ferguson <[email protected]> wrote: In reply to another thread the following comment was made: “ Importing a Gedcom is going to cause a slight loss of data because L7.5 does not export all of the fields. (L8 does a much better job for allowing you to use a Gedcom file as an archive.) That said, if you are using SourceWriter, Gedcom necessarily converts your sources to Basic sources. Still true in L8. “ This cannot be overemphasised. Whilst much testing was done on GEDCOMS too little of this effort (in my view) was spent on the problem that Legacy cannot satisfactorily import its own GEDCOM. It was inevitable that with a change in the database construct, together with a change in the default location for the Legacy folder, some users would use a GEDCOM to transfer their files (in both directions). So, apart from other (minor? but important to some) problems if one uses the SW sourcing *do not use a GEDCOM*. Ron Ferguson http://www.fergys.co.uk/ 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
