CiviCRM Community Forums (archive)

Our donor liaison has requested the ability to segregate our donors based upon age. Unfortunately, we do not know the birthdate of virtually any of our donors, and she doesn't want to start calling up donors to ask them their birthday (too creepy.)

I suggested rather than putting some kind of fictitious value into the "date of birth" field that we add a new field named something like "estimated age" or "approximate age" that would allow us group donors more or less by generation without putting known incorrect data into the standard "date of birth" field. I suppose we could even eventually configure a trigger to increment by one the value in this new field every year.

Does this seem like a reasonable approach, or is there another common way to handle this problem?

Thanks,

Glenn Gillis
IT Manager
Environmental Law Alliance Worldwide
http://www.elaw.org