Jenny wrote:
> When I opened my latest Gedcom in FTM, FTM didn't like that date format
> and dropped all dates in that style from the file. As it happened, it
> didn't really matter in this instance as I was just "playing around" but
> there might occasions when I want to retain the dates.
>
> Is this impossible because FTM doesn't recognise this format at all, or
> did I do something wrong in setting up the Gedcom export?
Certainly the Q style dates are retained in Legacy.
However, as you painfully found out, they don't go over to FTM
well, if at all. This is another reason for Legacy to add native
charting capability, to minimize and/or eliminate the need to use
other programs. I wonder if the add-ins handle these Q style
dates properly?
I can think of two workarounds and a fix.
Fix: Legacy developers come out with yet another switch on
GEDCOM export to convert all the Q dates to just give the year.
Workaound1:
Edit the GEDCOM to get rid of Q dates using search and
replace, after export from Legacy and before importing to FTM or
other.
Workaround2:
Create alternate dates using Q dates and leave the primary dates
as just the Year. That is only put Q dates in alternate BMD events.
Then on export, the primary will be read in properly.
jr
Enter the drawing for a FREE Legacy Cruise to Alaska or a FREE research trip to
Salt Lake's Family History Library. Open to users of Legacy 6 Deluxe. Enter
online at http://legacyfamilytree.com/FreeTrip.asp
Legacy User Group 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/
For online technical support, please visit
http://www.legacyfamilytree.com/Help.asp
To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
