Is there an eTapestry forum somewhere or will one eventlually be put here?

Have you done any searches for past posts on this topic.  This has been discussed a lot and it is always recommended you start there. I do not recommend ever having a donor code.  There is no need for it because you can always query on whether someone is a donor based on the presence of gifts on the record.  Therefore I code all ...

The place to start is A: figure out why they have had cleanup projects in the past and yet they are back here needing to do it again.  This sounds to me like a lack of a regular auditing process after the last cleanup and lack of policies and procedures (either lack of them being created or lack of them being followed).  I know you are ...

I hate to say this but I am SOOO confused. You recorded a pledge in RE.  Presumably Finance also recorded that pledge.  You get payments on that pledge.  You report to finance when these payments come in and tell them that they are pledge payments (not new revenue). Where is the double counting?

It may help to know how you report to finance your income.  I assume you are paying off the pledges in RE but when you send the cash to finance they can't tell what is new revenue and what is a receivable payment.  If so. is sounds like you are not using the GL distribution functions on your funds to have the proper GL codes show as ...

I also would be very careful about what information you put on a constituent record as the word is that whatever you put on there the donor may someday ask to see and you would have to show them.  I would ONLY put on an ethnicity/raceif self-disclosed by the donor such as in a survey.

I would not even attempt to try to make up my own list.  I would use a known list like this such as whatever the US Census Bureau uses.

I have never heard of any industry standards for this and each institution must decide on the heirarchy that best fits their needs.  I can say, however, that most often I have seen Alumni is at the top of the list if you are an educational institution.  From there they all vary most often because the types of constituent codes places use ...

Actually the final step would be deleting the solicit codes once you have confirmed that the attributes have all been added properly.  I do not recommend maintaining duplicate systems so I would completely remove the solicit codes and even delete the values from the solicit codes table so they can't accidentally be added in the wrong ...

And your work around would work but it would require him to always run two separate mail runs - one using a query of those with the solicit code and one for those without.  That would get on my nerves as a daily process but temporarily it would work.