Greetings everyone,
I am working on a major database clean-up and have hit an issue that has caused some frustration. I am including email addresses as a criteria, and I've noticed that members of a household often use the same email. I obviously don't want to merge Jane Smith and John Smith of the Smith household together even though they have the same email. Has anyone tried to edit the identify merge procedure to exclude constituents who are members of the same household? I keep experimenting with bits of code but I'm worried about excluding more than I want to. I would love to hear any suggestions if someone has dealt with this already.
Thanks!
Are these not A1/A2? I thought there was a check preventing merging of an A1 with an A2. Or maybe it's that: merging is prevented but adding to the list isn't?
The latter may be the case. From what I can tell, there is nothing in the Identify procedure that prevents them from showing up. I haven't actually tried to merge them, so they may be protected from actually being merged, but I really want them cleaned out of my potential duplicates list to make it easier to manage.
Thanks so much Gawain! This seems to be working in identifying the constituents I was looking for. And thank you also for your suggestion about this being a separate procedure that I run after the initial pull. I think that will definitely be the way to go.
You might want to add a check to make sure that the fname is not in fact identical before removing them from the list.
Good point...I'm on it! Thanks again!