I just loaded the new build this morning and I am running into some changes in the new build that will make a difference in how I go about doing things I don't know if these were intentional changes or a programming change that slipped by. I ask your patience as I try to explain, thank you.
First I keep three databases, my master db, a pruned db, and a direct line db. With previous builds I was able to create the pruned db by exporting to another legacy file, from the master to the pruned, select export all spouses of tagged individuals. For some reason this is no longer picking up other spouses. And has dropped about 500+ names from the pruned db. The reason for the smaller databases is that I use pocket genealogist and smaller files are better to work with. Example: One instance Joseph Jewett married a second time to Ann (unknown maiden) widow of Bozoan Allen. Ann is tagged, in exporting with this option selected it will not pick up her first spouse. In order to search for Ann I need to have Bozoan included I in the past, before the export to pruned and direct db's, "set" intellisync numbers so that when I do research using the smaller files I can easily merge them back into my master. The set feature is gone. Is this a intentional change (automatically done) or an error. I need to know, before I go on researching using the new converted database about these changes or should I reload the previous build and restore the old database, until the next build? I am sending this both to support and to the newsgroup, maybe someone out there has an easier way also. Thank You Randy C Mack www.MacksShack.com Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
