This is an area of Legacy that functions in a way that is not at all user-intuitive in spite of suggestions over many years to eliminate the confusion!
As has already been mentioned, when an EXPORT is selected, Legacy creates an empty database which contains all the default values/settings. Unfortunately from that point on Legacy's programming looks at everything from the viewpoint of an IMPORT into that empty database. When an event is exported to that "empty" file and the exported event doesn't match the default definition value(s), Legacy opens up a very unnecessary and ridiculous window which mentions an IMPORT replacing an existing event. Obviously since this is an EXPORT to a supposedly empty database, Legacy should automatically replace the empty database's default value(s) with the imported values. But instead, it confuses the user with words referring to an IMPORT and these apply to the way it is programmed instead of words that apply to what the user is doing. If you are exporting to an empty file and the Combine Event Definition window appears you need to click on "For this import, always overwrite the existing event with the incoming event" Cheers, -- Dave N. -- David Naylor, Halton Hills, Ontario, Canada. --- Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
