Curt points out a problem that most people and software products don't know how to resolve. What data goes where!
It is NOT wrong to place cemetery names, church names and street addresses at the beginning of the "PLACE" field, except when the program you are using says that it is wrong.
But it is right when the product you are using says it is right!! Every program has it's own way to do things that are niether right or wrong just inconsistant. And for most people that inconsistancy will never be seen unless they evaluate, change or use other people's software or receive a GEDCOM for another program.
Curt will find that if he moves to another program having the cemetery names, church names and street addresses in the "Description" field will probably cause him to move the data again, because this field does not always exist in every program and it is very likely not put in the GEDCOM correctly by FTM.
** I Never Except a GEDCOM from Outside my Program **
For two reasons:
1) My program is very GEDCOM compliant and most other programs are not, therefore data will not be in the right place.
2) My standards for data entry and accuracy are very strict while most other people's are not. I like to review each piece of data and therefore if I'm reviewing it, why not enter it as I review?
I once used Generations and the GEDCOM it created was very poor and most data was not imported correctly by my next program PAF. Much of this data from PAF was then not imported correctly by the next program I used.