Instead of exporting, can you try this: Make a copy of your tree with a new name, Edit THAT copy to remove the branches you do not need. Can this work?
On Mon, Feb 20, 2017 at 9:48 AM, Brian Kelly <[email protected]> wrote: > The only way to retain SourceWriter sources is to export to a New Legacy > File not to a GEDCOM. You can elect to export a tagged group as a New > Legacy file on the Options for records to export. > > Brian Kelly > > > On 20-Feb-17 9:40 AM, Cliff Gittens wrote: > >> I have a large database of about 56,000 records. I want to split the >> database into seperate families that are not related. >> >> I tried tagging several thousand individuals who were all related into a >> single family, some 7,000 people, created a gedcom for Legacy and then >> imported these records into a new Legacy database file using the >> gedcom. One of the problems in doing this, is that sources in the >> larger database which were created using the source writer method >> reverted back to basic sources in the new smaller database file. >> >> Does anyone know of a way to split a Legacy database file into smaller >> Legacy Dataebase files and not loose the Source writer type sources? >> >> Thank you >> >> Cliff Gittens >> >> >> >> >> >> >> > > -- > > LegacyUserGroup mailing list > [email protected] > To manage your subscription and unsubscribe http://legacyusers.com/mailman > /listinfo/legacyusergroup_legacyusers.com > Archives at: > http://www.mail-archive.com/[email protected]/ >
-- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
