I got a reply from Ancestry support saying it is a known issue in the programming for FTM 2010 and will likely never be resolved. Their solution is to upgrade to FTM 2012 which doesn't exhibit the problem.
Thanks for your suggestion to completely remove FTM10 before installing 12. That will save me a lot of time.
Thanks for your suggestion to completely remove FTM10 before installing 12. That will save me a lot of time.