Search for content in message boards

Wish I had signed up for the beta

Replies: 35

Re: Also Known As Fact - Effects in FTM

Posted: 20 Aug 2013 10:13AM GMT
Classification: Query
Edited: 20 Aug 2013 10:50AM GMT
silverfox,

I hear where you are comming from regarding the current state of FTM and data entry. If I was only a FTM user I would probably follow your process as well, not because you are doing it but because it is the only possibility with FTM.

However, this thread is more geared toward the thought that if FTM is changing to make AKA a full name with surname, given name etc. This is not a good design decision not just from a GEDCOM view but from a database view. Having two field both representing a name but stored differently is very troubling.

Then putting GEDCOM on top of that, I still can't import my very large database with compliant GEDCOM. I spent a lot of time when I moved off my two previous software packages (Generations and PAF) dropping the stand alone AKA and married name fields to using recurring name tags, now to loose them when I import into FTM is very wrong.

This is just one of the many design decisions FTM made that were probably based on the wrong people driving the process.
SubjectAuthorDate Posted
tony_knight 20 Aug 2013 1:48PM GMT 
KATHYMARIEANN 20 Aug 2013 3:33PM GMT 
silverfox3280 20 Aug 2013 3:21PM GMT 
silverfox3280 20 Aug 2013 3:38PM GMT 
tony_knight 20 Aug 2013 4:10PM GMT 
kj_norway 20 Aug 2013 4:13PM GMT 
AGHatchett3rd 20 Aug 2013 4:24PM GMT 
dmossfritch 20 Aug 2013 4:44PM GMT 
kj_norway 20 Aug 2013 5:04PM GMT 
kj_norway 20 Aug 2013 5:17PM GMT 
per page

Find a board about a specific topic