For the last several weeks, I have been having problems with merging census records into my file. If I click on a leaf behind the name of someone in the family mode, I quickly pull up a list of hits. If one of the hits is a census record and if I click on it, the names and data from the census report line up opposite those from my file at the bottom of the window. The little tail begins to spin and the word "Merge" is grayed out. This process continues for about 4 and a half minutes until the tail quites spinning and the word "Merge" blackens.At that point I can finally merge the census record into my file. What is so odd about this is that at any time during the 4 and a half minutes, I can click on the underlined title of the census report above and view the original image of the report, so the report is there, even though I can't merge it. I am not 100 per cent sure when this began, but sometime after Christmas. I've talked to four level two techs at Ancestry, and each has had me do something or other, including one who said that I should get the 2012 version, which I did, but the new version has exactly the same spinning and slow merging problem inherent in 2011.The new version did NOT cure the spinning problem! Another tech had me remove my Norton Internet Security, open my Windows Firewall, clean out my caches, and update Java. In the process, I lost the rest of my Norton subscription, as it was already installed on my HP that I bought last August (and it came without a Norton CD). He also suggested that there is probably something wrong with my ".net framework." Yesterday, I spoke to still another tech who had me check to see whether I have the most recent ".net framework." I do. Then she tried to duplicate the same search that I was complaining about, and she immediately disovered that she was having exactly the same problem with the tail spinning and the word "Merge" grayed out for several minutes. She said that she had not had any other complaints about this specific problem. She said she would work on it and get back to me with a solution. Have any of you had this same problem? Have you been able to fix it?