@F2193@ is the form used by the exporting program for the gedcom identifier of MRIN.
Look in the Marriage List. Also, when importing it is a good idea to *not* renumber the RINs/MRINs (fill all existing abandoned RINs/MRINs) because the log uses the original RINs/MRINs from the gedcom and you will not be able to location them in the file if there is something to find. I always import with all the original RINs/MRINs and then renumber later, if necessary. However.... if you're importing a gedcom into your main Family File (and you should *not* do that - I'll explain in a minute), then the imported RINs/MRINs will be changed in order to preserve your existing RINs/MRINs. Why not directly into your Family File? You should always import into a new file - verify the data, clean it up and make sure it's something you *really* want in your Family File. *Then* import that new Legacy file into your Family File if you want that data in there. Sincerely, Sherry Technical Support Legacy Family Tree On Fri, Oct 5, 2012 at 7:33 AM, Pat Hickin <[email protected]> wrote: > In taking a look at my gedcom error report, most of the entries had to do > with individuals, and gave the RIN (e.g., Main Record:0 @I1472@ INDI) > No problem. > > but I quote the last three entries: > > Main Record:0 @F2193@ FAM > * Unrecog. Date: gest aft 1780 > Main Record:0 @F2199@ FAM > * Unrecog. Date: gest by 1748 > Main Record:0 @F2223@ FAM > * Unrecog. Date: gest 1780 > > I don't know how to find these F#s. > > Pat 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
