I had been having MAJOR crashing problems with the merge feature using FTN2012 and being up in ACOM to find and ultimately add/merge fact to a person. As of yesterday, the ACOM software folks must have made progress on that part of the problem (which I think is related to the merge problem). My system is not crashing. The ACOM software folks must have been working on this crashing issue.
BUT..........Still there is the problem with newly added names on FTM, they seem to be on the ACOM family tree (after the latest sync), but not available to add/merge feature to add the fact (such as a US Census)via the use of the "Save" \/ button at the bottom!
 On FTM I constantly backup, compact and sync. All my browsers cashes are clean. Cookies set correctly etc etc.
 I find a Fact like the 1920 Census.
 Via the "Save" button, I attempt to add/merge it to a person.
 ACOM asks if I want to attach to someone OR save to shoebox.
 I leave the dot in the "attach" to a person command, then click on the "Continue" button.
 ACOM asks me to key in the name I want to attach it to.
 Keying in the name, USUALLY if it is a name added recently (not a week ago), the list of suggestion names DOES NOT have the NEWLY added name there (or the new updated name if one has changed it from a week ago (such as adding a maiden name or a middle initial, the recently updated FTM name IS NOT updated on ACOM, despite being sync'ed). NOTE: if I go to my newly sync'ed ACOM tree, the updated name IS there updates or added. BUT..........Is not in the list of suggestions mentioned above.
 IF a previously added name (like a week ago) IS in the list of suggestions, I click on the "Attach" button.
 ACOM takes one to a screen where the following error message is displayed:
"Some tree features are temporarily unavailable. During this time you may not be able to add new information to your tree. Thanks for your patience while we resolve this issue."
 STILL doing this today Sunday 04/21/2013.
 So let's see if they can fix this?
So far so good on the crashing!
ACOM folks, find this problem and we are there.
Lake Oswego, Oregon