I have major issues with the "new" algorhythm. It takes much too long to run - overnight--really? And it brings up records that have almost nothing in common. It also does not find the duplicates it should find. As an example, at the end of June my database was virtually duplicate-free (yea me) and after the upgrade, I had to have Blackbaud support run my duplicate constituent report. Not only did it take them several days to get it-I had to authorize them to use a back-up of my data. then the dang thing is 500+ pages long. We are used to running this report monthly. I have since found it necessary to export data out to Access in order to search for duplicates. This is not efficent.

Erin - have you not searched the Ideabank for the dozens of other suggestions for the issues with the duplicate constituent report?

Melissa, these are just workarounds. I also think that something as crucial to our data health as duplicate report shouldn't have been left broken for 6 months now.

7.92 patch 6 has resolved the worst of the duplicat report problems and the new report has helped us find several hundred "real" (not false alarm) duplicate records that the previous report missed. But having the old method as an option would be nice (and I'm sure the folks at Blackbaud are wishing they'd done so for the first release of 7.92).