I would like to take a moment and point out that the problem of dates by FTM2012 has been further complicated during the last 48 hours as a result of code changes to the Ancestry.com websites.
As you will see from the attached image, the dates corrupted by FTM2012 that were subsequently uploaded to Ancestry without user control or option during the synchronization process, now NO LONGER DISPLAY in Ancestry Member Trees at all.
For the present time, there is no fix to this problem short of modifying one-by-one the corrupted dates. FTM2012 does not allow Find & Replace operations in the date fields, and even if it did, it would again automatically convert all dates back to the only format it wants, without allowing user control, which is the date format we would be trying to replace.
There is a total disconnect between the development teams that work on Ancestry.com and FTM2012, with no one apparently talking to each other, and users' data caught in the crossfire between the two.
Have you inspected your data on Ancestry since you last synchronized?