Page 1 of 1

TMG import problem with Place names

Posted: 10 Jan 2016 21:36
by d_c_weber
Placenames are messed up

I have imported from UFT to TMG9 and then imported from TMG9 to FH6.1.
All of my place names were in order as city, county, state, country. Thus, the UFT worked well, since it used these 4 designations, plus a field for the burial cemetery and the gravesite location within that cemetery.
But, now I see that FH only has 3 designations for places. i.e. part 1, part 2, part 3
So, in the UFT, I had the place as " Toledo, Lucas county, Ohio, USA" as the place at a gravesite in Toledo Memorial Park cemetery, now it says: part 1 = "Toledo Memorial Park Cemetery||sec A", and part 2 = "lot 29", and part 3 = "grave 2, Toledo, Lucas county, Ohio, USA".
I have 10's of thousands of events and places in my database!! How do I get this fixed?
What I want is some designation that gets the locations in way such that the city is one field (Toledo), the county is another field (Lucas County), the state is another (Ohio), and the country is a fourth field (USA), and then some notes about the cemetery (i.e. Toledo Memorial Park Cemetery) and the location within the cemetery (e.g. sec A, lot 29, grave 2). Maybe as a note to the fact.
Is there a way to redo the import so that this works? [It will take me half a lifetime to fix this otherwise.]

Re: TMG import problem with Place names

Posted: 10 Jan 2016 22:10
by LornaCraig
But, now I see that FH only has 3 designations for places. i.e. part 1, part 2, part 3
FH can have up to ten place parts, it's just that the default is set to three. Use Tools>Work With Data>Places then click Columns. There you can set the number of columns (parts) you require.

Re: TMG import problem with Place names

Posted: 10 Jan 2016 22:13
by d_c_weber
So, how many placenames should I set FH to?
Then, do I reimport the TMG data?

Re: TMG import problem with Place names

Posted: 10 Jan 2016 22:16
by tatewise
You can change it any number of times until you are happy.
Sounds like you need 6 or 7.
No import required.
All FH is doing is looking at the comma separators, and the Column Parts you choose.

Re: TMG import problem with Place names

Posted: 11 Jan 2016 21:49
by DonF
It sounds like you are using GEDCOM to do the transfer from TMG to FH.
Always use the direct import option for TMG imports - it produces a better result in many ways and I have never adjusted the number of place fields - I presume (on direct import) that FH works out for itself what to do.